If your webhook endpoint doesn't respond with HTTP 200, Swipe Aras automatically retries delivery with exponential backoff.
Retry Schedule
Attempt | Timing |
|---|---|
1 (initial) | Immediate |
2 | 5 minutes after failure |
3 | 30 minutes after failure |
4 | 2 hours after failure |
5 | 8 hours after failure |
After 5 failed attempts, the delivery is marked failed and no further retries occur. Failed deliveries are logged and visible in your Webhooks dashboard.
What Counts as a Successful Delivery?
Your endpoint must return an HTTP 200 OK status code. Any other response code (including 201, 202, 4xx, or 5xx) is treated as a failure and triggers a retry.
Delivery Logs
Every delivery attempt is logged with the full request and response body, so you can inspect exactly what was sent and what your server returned. Access delivery logs from Developer → Webhooks in your dashboard.
Best Practices
Respond quickly: Return 200 immediately after receiving the webhook, then process the payload asynchronously. Don't block the response on your business logic — slow responses may timeout and trigger retries.
Handle duplicates: If a retry is delivered after your first successful processing, your handler should be idempotent (safe to run twice without side effects).
Use the event ID: Each webhook payload includes a unique event ID — use it to deduplicate retries.