Respond quickly
Your webhook endpoint should return a2xx status code as quickly as possible, ideally within 5 seconds. If your processing takes longer, acknowledge receipt first and process the data asynchronously.
Implement idempotency
Numero may send the same webhook more than once (e.g., due to network issues or retries). Use theid field to detect duplicates:
Use HTTPS
Always use an HTTPS URL for your webhook endpoint. HTTP endpoints will not receive webhooks in production.Verify signatures
Always verify the webhook signature in production. See Webhook Signature Verification for implementation examples.Handle failures gracefully
If your endpoint is temporarily unavailable, Numero will retry delivery with exponential backoff for up to 24 hours. After 10 consecutive failures, the webhook subscription is automatically disabled. Make sure your endpoint can handle:- Delayed deliveries
- Out-of-order events
- Duplicate events
Rate limits
| Limit | Value |
|---|---|
| Webhook deliveries | 25 requests per second per account |
| Management API calls | 100 requests per minute per account |