POST request with the event payload.
Delivery includes automatic retries with exponential backoff.
Need to set up a webhook destination? Follow the steps in Getting Started.
Requirements
Your webhook endpoint must meet these requirements:Event Types
All destinations automatically receive every event type. There is no per-event filtering.state_change
Service request state changed — QC, authentication progress, or final result.
media_rejected
Uploaded images rejected during quality control.
invalidate_sr
Service request cancelled or cannot be processed.
Common Payload Fields
Every webhook event includes these base fields:Retries
Failed deliveries (non-2xx response or timeout) are automatically retried with exponential backoff:
After all retries are exhausted, the message is marked as failed. You can view delivery status and retry manually from the Developer Settings.
Testing
If you don’t have an endpoint ready yet, you can use Svix Play to generate a temporary webhook URL for testing. Paste the generated URL as your webhook destination in the Developer Settings, send a test event, and inspect the payload in real time.Next Steps
Event Types
Detailed payload schemas for each event type.
Handling Webhooks
Code examples, best practices, and security guidance.