Webhooks: send matches to your own system

A webhook posts a JSON payload to a URL you control whenever a saved search finds new matches. Webhooks need a Pro plan (or the Pro trial). Set them up on your Webhooks page.

Set one up

1. Click Add Webhook.
2. Enter a Name and the Webhook URL.
3. Optionally add a Signing secret so you can check requests really came from us.
4. Optionally choose a Saved search. Leave it blank to fire for all of them.
5. Click Create, then Test. You will see "Test successful" with your endpoint's status code.

What you receive

A POST with Content-Type: application/json. The body has event ("new_matches"), search_name, match_count, fired_at and a companies list. Each company has its number, name, status, type, incorporation date, registered address, sector codes, current directors (name, role, appointment date) and any verified website or contact details.

Check the signature

If you set a secret, every request carries an X-NewcoHunter-Signature header: an HMAC-SHA256 hex digest of the raw request body, using your secret as the key. Compute the same value on your side and compare. Requests also send User-Agent: NewcoHunter-Webhooks/1.0.

Failures

• Reply with any 2xx status within 10 seconds to count as delivered.
• Anything else counts as a failure.
• After 10 failures in a row the webhook is switched off. A success resets the count.
• Re-enable it from the Webhooks page once your endpoint is healthy.

Not the same as signal webhooks

These webhooks follow your saved searches. Signal webhooks, which push events like new lending or new directors, belong to the Signals API. See API and developers.

Prefer no code? Use Zapier.