Webhooks

Email searches and verifications run in real time, typically taking 5–15 seconds. However, they may take longer if a company's SMTP server or website are slow.

Instead of waiting for the request to complete (synchronous processing), you can use webhooks to receive the results asynchronously once they are ready.

How to Use Webhooks

To receive results via a webhook, include an x-webhook-url header in your API request. This header should contain the publicly accessible URL where you want to receive the results.

Matching Webhooks to Requests

When the x-webhook-url header is present, the API responds immediately with the request id:

{
  "request_id": "e5394aa0-9f1d-4a92-a864-d9d57bf85da3",
  "webhook_url": "https://yourdomain.com/webhook"
}

Store that request_id on your side. The webhook body contains the result only, so the id travels in the x-request-id header of the webhook request, which is how you map the result back to the request that produced it.

Every webhook request is sent with the following headers:

user-agent: Anymailfinder-Webhook/5.1
x-request-id: the request id returned when you made the request
x-response-status: the HTTP status code the synchronous request would have returned
x-webhook-url: the URL you provided

Supported Endpoints

Webhooks are available for the following API endpoints:

We recommend checking the specific endpoint documentation for guidance on handling webhook responses effectively.