Why Use Webhooks?
| Approach | Latency | Complexity | Use Case |
|---|---|---|---|
| Polling | Seconds to minutes | Simple | Low-volume, non-critical |
| Webhooks | Sub-second | Moderate | Real-time updates, high-volume |
Configure Webhooks
Configure in Hub: Webhooks → Add Webhook Endpoint URL: e.g.,https://api.yourgame.com/webhooks/immutable
Events: Mints, transfers, orders, trades
Webhook Payload
Verify Webhook Signatures
Retry Policy
Exponential backoff on errors:| Attempt | Delay |
|---|---|
| 1 | Immediate |
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 30 minutes |
| 5 | 2 hours |
Best Practices
Respond quickly
Respond quickly
Return a 200 response immediately, then process the event asynchronously. Webhook requests timeout after 30 seconds.
Handle duplicates
Handle duplicates
Use the
event_id to deduplicate events. The same event may be delivered more than once.Secure your endpoint
Secure your endpoint
Always verify the webhook signature. Use HTTPS for your endpoint.