MuleSoft · Rate Limiting policy
429 Quota exceeded
An API protected by the Rate Limiting policy returns 429 Quota exceeded when the request quota for the current time window is used up. Requests are blocked until the window finishes, so wait for the window to reset or raise the limit in the policy.
VerifiedLast verified
01Error text
429 - Quota exceeded, requests are blocked until the current window finishes02Likely causes
- The request quota for the current window is used up.
03How to fix it
- Wait for the current window to finish. Requests are blocked until then.
- Turn on Expose Headers in the policy to let clients see
X-Ratelimit-Remaining,X-Ratelimit-LimitandX-Ratelimit-Reset. They are off by default. - Raise the number of requests or change the time period in the policy if the limit is too low for legitimate traffic.
- To protect a backend from bursts, the docs point to the Spike Control policy.
iNotes
For WSDL APIs on Mule, the policy returns 400 for SOAP 1.2 and 500 for SOAP 1.1 when the quota is exceeded. The docs advise longer windows in clusters.
04Official documentation
→Related errors
- 401 Unauthorized or invalid client application credentialsAn API protected by the Client ID Enforcement policy returns 401 when the client application's credentials are missing, invalid or not authorized. The client needs an approved contract for the API and must send matching credentials on every request.
- HTTP:TOO_MANY_REQUESTSHTTP:TOO_MANY_REQUESTS means the server received too many requests from your app in a given amount of time (HTTP 429). Send fewer calls at once and retry after a delay.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer