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

Workato error
429 Too Many Requests

02Likely 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

  1. Configure the sending system to retry webhooks until they are accepted. This is the documented best practice for 429 responses.
  2. Use the response headers to pace retries: Retry-After appears only in rejected requests, and X-Rate-Limit-Remaining, X-Rate-Limit-Reset, X-Byte-Limit-Remaining and X-Byte-Limit-Reset report the quota.
  3. Reduce the event rate or payload size at the source if it regularly exceeds the quota.
  4. 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

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.