In a Nutshell
Max 50 requests / min.
Otherwise you’ll get a
429 Too Many Requests.Max 100MB payload size
Our server cuts the connection and returns an error if the request content length exceeds 100MB.
Time-out
Any request that takes more than 5 seconds will be aborted by our server.
2 months events retention
Events (webhooks) are kept for up to 2 months, whether delivered or not.
3 seconds timeout on webhooks
Events are sent to webhook-endpoints through POST requests that have a 3 seconds timeout. If there are retry attempts left, then the event will be planned for a retry later.
5 events delivery retries
Failed event deliveries are retried up to 4 times (so, at most, 5 delivery attempts) over ~24 hours after the initial attempt. Keep in mind you can always trigger additional manual retries.
Errors Due to Limits Exceeded
Your integrations may encounter errors due to server limits being exceeded.| Description | Response HTTP status | What you should do | Should you retry? |
|---|---|---|---|
| Request took too long (> 5 seconds). | 408 Request Timeout | Your request may be too complex. | ✅ Yes (simplified) |
| Request body too large. | 413 Content Too Large | Send us smaller files or data. | ❌ No |
| More than 50 requests in a 60 seconds window. | 429 Too Many Requests | Space out your requests. | ✅ Yes (later) |
| Request headers are too long (> 8 KB). | 431 Request Header Fields Too Large | Check your headers, you should not encounter this error in a normal case. | ❌ No |
These limits values may be changed without prior notice, as long as they become higher (i.e. more lenient).