Webhooks Reference
How they work
Webhook URLs will receive a POST request with JSON data related to the event that triggered the webhook.
See Events below for supported events and the associated JSON payloads.
Error handling
There are things that can go wrong even before a request reaches its destination (e.g. DNS resolution error, sudden network failure, etc.) and even if it does, the target system may not always be able to correctly process the request. This is why the notification delivery system is built to handle these failures.
Our webhook delivery system uses response status to determine whether a request has been successful or not.
2XX response codes: The request is considered successful and the notification is considered as delivered, no retry needed.
Any other response status or error (such as connection error, timeout, etc.) is handled as an unsuccessful delivery attempt and the task is rescheduled for later.
Retries
If a webhook delivery fails, it gets retried. We use an exponential backoff strategy to determine how long to wait before attempting the delivery again.
We'll retry a webhook delivery up to 20 times, after which the delivery will be marked as retries exhausted
and retries will stop.
Events
screenshot_set.approved
screenshot_set.approved
This event is fired when a set of screenshots is ready for download
Objects
ad
ad
This object contains data about the ad
creative. Notable fields include:
status
status
screenshot
screenshot
This object contains data about the screenshot
. Notable fields include:
status
status
Last updated
Was this helpful?