How Webhooks Work
- You configure a webhook endpoint URL in your Fanfare dashboard
- When an event occurs, Fanfare sends an HTTP POST request to your endpoint
- Your server processes the event and responds with a 2xx status code
- If delivery fails, Fanfare retries with exponential backoff

Webhook Payload
All webhook payloads follow a consistent structure:Payload Fields
Event Categories
Queue Events
Draw Events
Auction Events
Order Events
Consumer Events
Distribution Events
Configuring Webhooks
Via Dashboard
- Navigate to Settings > Webhooks in your Fanfare dashboard
- Click “Add Endpoint”
- Enter your webhook URL (must be HTTPS)
- Select the events you want to receive
- Save the endpoint
Via API
Receiving Webhooks
Basic Handler
Async Processing
For production, process webhooks asynchronously:Webhook Headers
Each webhook request includes:Best Practices
1. Respond Quickly
Respond with a 2xx status code within 30 seconds. Process events asynchronously for longer operations.2. Handle Duplicates
Webhooks may be delivered more than once. Use the eventid to deduplicate:
3. Verify Signatures
Always verify the webhook signature before processing. See Webhook Signatures.4. Use HTTPS
Webhook endpoints must use HTTPS. HTTP URLs will be rejected.5. Handle Retries
If your endpoint fails, Fanfare will retry. See Retry Policy.Testing Webhooks
Using the Dashboard
- Go to Settings > Webhooks
- Select your endpoint
- Click “Send Test Event”
- Choose an event type to test
Using CLI
Local Development
For local development, use a tunneling service:Webhook Events Reference
For detailed information about each event type and its payload, see:- Webhook Events - All event types and payloads
- Webhook Signatures - Signature verification
- Retry Policy - Retry behavior