Search monitoring is an opt-in beta for France. Contact support@topograph.co to request access. It complements company monitoring, which tracks changes to a company you have already identified.
Create a watch
query contains the company name, without its address. Every name word must match. Capitalization, accents and punctuation are ignored; partial words are not matched. Each supplied city or postal code must match, and each word in an optional addressLine1 must appear in the address. A missing address field cannot satisfy that constraint.
Use a specific name. An overly broad search is rejected rather than watching an incomplete list of results. The beta allows 100 active watches per account. Watches expire after 30 days by default; supply an ISO date-time in expiresAt for an earlier expiration.
The response contains the watch’s id, status, expiration and initialMatches. On first creation, those matches form the starting baseline: inspect them immediately if the company may already have registered. They do not trigger new-match notifications. Reposting the same name and address returns the existing watch and its remembered matches; it does not create a second watch or extend an active watch’s expiration. Supplying metadata replaces its metadata.
Receive a match
New matches producesearch_monitor.match events at your configured webhook endpoint:
id to request company data and available documents separately.
Checks run hourly. Register publication and data availability determine when a company can be detected, so this is not an immediate registration alert. A previously seen company that disappears and returns does not create another match event.
A failed check preserves the previous results and sets lastError on the watch, for example when a name grows to match too many companies. Checks continue hourly and lastError disappears once one succeeds. To narrow a watch, stop it and create one with a more specific name or address.
Webhook delivery can be retried. Deduplicate using eventId, and follow the webhook verification guide. Updating watch metadata does not change events already queued for delivery.
Manage watches
A match leaves the watch active so you can review multiple candidates. Stop it once you have identified the company. Reposting an expired or stopped watch restarts it for the requested duration with a fresh baseline: companies that appeared while it was off are returned in
initialMatches, not sent as new matches.
Test in a development environment
Development accounts can use the API without beta activation. Watches see only that account’s company fixtures. Create the watch first, then add a matching fixture to make a new candidate appear at the next check. Events carryenvironment: "development".