Skip to main content
Every campaign has its own webhook. From here you turn delivery on, point to the endpoint that will receive the real-time HTTP notifications, and check what has been delivered.
The panel lives in Settings (side toolbar) → Webhook.
Webhook configuration screen in Exoid

Webhook configuration screen

​
Panel fields

​
toggle
Turns automatic delivery of HTTP requests on or off for this campaign.
​
url
required
Full address of the endpoint that will receive the requests, for example https://yourdomain.com/webhook.
​
string
The secret used to digitally sign every payload with HMAC-SHA256. See Signature and security to implement verification.

​
Webhook Requests

Below the fields you’ll find the chronological list of every call made. For each row you see: Failed requests are logged too, with the status code that made them fail.

​
Quick actions

Use Test Webhook before publishing your study: it confirms that your endpoint answers 200 and that signature verification works, without putting real responses at risk.

​
Technical details of the request

If your endpoint doesn’t respond within 30 seconds, the request is considered failed and falls into the retry logic. Answer 200 immediately and process the payload asynchronously.

​
Next steps

Signature and security

Recompute the HMAC-SHA256 signature and reject requests that aren’t authentic.

Payload reference

What the JSON you receive contains, field by field.

Related topics

July 1, 2026Question typesFebruary 18, 2026