MuleSoft · Spike Control policy
429 from the Spike Control policy
An API protected by the Spike Control policy returns 429 when the request found no quota in the window and was still rejected after the configured number of retries. Slow the caller down, or adjust the policy's limit, delay and attempts.
VerifiedLast verified
01Error text
429 - The number of requests by HTTP APIs exceeded the configured limit. Request rejected after specified number of reattempts.02Likely causes
- The number of requests exceeded the configured limit for the time period.
- When the window has no quota left, the request is queued and retried. It is rejected after Delay Attempts retries, each Delay Time in Milliseconds apart.
03How to fix it
- On the client side, lower the request rate or retry later.
- In API Manager, review Number of Reqs, Time Period, Delay Time in Milliseconds, Delay Attempts and Queuing Limit for the policy.
- Turn on Expose Headers to return
X-Ratelimit-Remaining,X-Ratelimit-LimitandX-Ratelimit-Reset, so clients can pace themselves.
iNotes
WSDL APIs get 400 (SOAP 1.2) or 500 (SOAP 1.1) with the same wording. The docs say the policy exists to protect the API and its parameters should be set to the lowest possible value.
04Official documentation
→Related errors
- 429 Quota exceededAn 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.
- 429 Quota exceeded (Rate Limiting: SLA-Based)An API protected by the Rate Limiting: SLA-Based policy returns 429 when the client application has used up the quota of its SLA tier for the current window. Wait for the window to finish, or move the client to a tier with a higher limit.
- 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