Workato · Webhooks
429 Too Many Requests (webhook gateway)
Short answer
Workato's webhook gateway returns 429 Too Many Requests when incoming webhook events exceed both the steady rate and the burst allowance. The sender should retry the webhooks until they are accepted, using the Retry-After header.
VerifiedLast verified
01Error text
429 Too Many Requests02Likely causes
- Events above the steady rate consume the burst allowance. Once both are exceeded, the gateway returns 429.
- Rate limit per environment: a steady rate of 20 events per second, equivalent to 72,000 events per hour, with a burst allowance of 9,000 events.
- Byte quota: 30 MB per minute, with a burst allowance of 30 MB.
03How to fix it
- Configure the sending system to retry webhooks until they are accepted. This is the documented best practice for 429 responses.
- Use the response headers to pace retries:
Retry-Afterappears only in rejected requests, andX-Rate-Limit-Remaining,X-Rate-Limit-Reset,X-Byte-Limit-RemainingandX-Byte-Limit-Resetreport the quota. - Reduce the event rate or payload size at the source if it regularly exceeds the quota.
- For sustained high volume, contact Workato support. Quotas may be adjusted per customer, subject to commercial terms and approval.
iNotes
Quotas are set at the workspace level. The docs state a different burst allowance of 18,000 events for legacy customers.
04Official documentation
→Related errors
- 400 Bad Request on webhook eventsA webhook event sent to Workato gets a 400 Bad Request when its payload does not match the Webhook type configured on the trigger, or is not UTF-8 compatible. Match the Webhook type to the payload, or use Raw Binary Data for non-UTF-8 content.
- concurrency limit exceeded / rate/quota limit exceededA Workato API platform endpoint returns 429 with concurrency limit exceeded or rate/quota limit exceeded when the client goes over a limit set by its access policy. Slow the client down, or raise the limit in the access policy.
- err.http.response.client_error.too_many_requestsThe Workato error type err.http.response.client_error.too_many_requests means an HTTP connector request received a 429 response from the external API. Workato's documentation marks 429 as an error a retry can resolve, so retry the step after a delay.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Workato work:Open Workato jobsWorkato rates and salariesHire a senior Workato developer