Webhook events notify your application when specific actions occur in your 1Money account. Your endpoint must respond with a 2xx status code within 10 seconds.
Retry Policy
If your endpoint does not respond with a 2xx status code, we retry the webhook delivery. The default policy allows 5 total attempts: the initial delivery plus 4 retries. Each delay below starts after the preceding failed attempt:
| Retry | Delay |
|---|---|
| 1st | ~30 minutes |
| 2nd | ~1 hour |
| 3rd | ~2 hours |
| 4th | ~4 hours |
After the fifth failed attempt, the delivery is marked as permanently failed. The default retry delays total approximately 7.5 hours, plus up to 5 minutes of jitter per retry and request/processing time. These are the default settings; the effective schedule depends on the configured delivery policy.
To inspect delivery outcomes and replay a missed notification, use List Webhook Events and Replay Webhook Event.
Best Practices
- Respond quickly - Return
200 OKimmediately, process asynchronously - Verify signatures - Always validate
X-Webhook-Signaturebefore processing - Handle duplicates - Use
X-Webhook-Event-Idfor idempotency - Use HTTPS - Webhook endpoints must use HTTPS
- Log deliveries - Track
X-Webhook-Delivery-Idfor debugging