POST request to your configured URL with the enrichment results.
Setting Up Your Webhook URL
Configure your default webhook URL in Settings → API. This URL applies to all API requests made with that key. You can also enable Send All Callbacks to receive webhooks for all enrichment activity on your account, not just requests made through the API.Your webhook endpoint must be publicly accessible and return a
200 status code to acknowledge receipt.Handling Webhook Requests
Respond quickly with a200 status code to acknowledge receipt. If your processing takes time, accept the webhook first and handle the work asynchronously in a background job.
Use status.code to check for success (200) or failure (400). For the full response schema, see the Individual Reveal documentation.
Overriding the Webhook URL Per Request
You can override the default webhook URL on a per-request basis by including acallback_url parameter in your Start Individual Reveal request.
Webhook Payload
Endpoint:POST {your_webhook_url}
Wiza sends a webhook when an Individual Reveal completes or fails. The request is a POST with a Content-Type: application/json header sent to your configured URL or the callback_url specified in the request. The data object contains the same enrichment results as the corresponding GET endpoint.
Individual Reveal Payload:
status.code will be 400. The data object contains the same fields as a successful response, with a fail_error field indicating the failure reason.
Verifying Webhook Signatures
Webhook requests include anx-auth-key header containing a SHA256 hash of your API key. Use this to verify the request originated from Wiza.
Retry Behavior
If your webhook endpoint returns a non-2xx response, Wiza will retry up to 3 times. Ensure your endpoint is available and returns a200 status code to acknowledge receipt.
If a webhook consistently fails (returns 404 or 403), Wiza will stop retrying for that request.
Related
- Status Codes & Errors — Handle API responses
- Authorization — Authenticate your API requests

