Skip to content

Handle Rate Limiting Errors

When your application exceeds rate limits, the API Gateway returns HTTP 429 (Too Many Requests) responses.

Recognizing Rate Limiting Responses

When a request is throttled, you receive an HTTP 429 Too Many Requests status code with a response body containing details about why the request was blocked.

Example throttled response:

{
    "code": "900800",
    "message": "Message throttled out",
    "description": "You have exceeded your quota"
}

Rate Limiting Error Codes

The error code in the response indicates which specific limit was exceeded:

Error Code Error Message Description
900800 Message throttled out The maximum number of requests that can be made to the API within a designated time period is reached and the API is throttled for the user.
900801 Hard limit exceeded Hard throttle limit has been reached
900802 Resource level throttle out Message is throttled out because resource level has exceeded
900803 Application level throttle out Message is throttled out because application level is exceeded
900804 Subscription level throttled out Message throttled out due to subscription level throttling limit reached.
900805 Message blocked Accessing an API which is blocked on user, IP, application, or API Context.
900806 Custom policy throttled out Message throttled out due to exceeding the limit configured through the custom throttling policy rules.
900807 Message throttled out Messaged throttled out because of exceeding the burst control/rate limit (requests per second) in the subscription level policy.

For complete information on all error codes, see Error Handling.

See Also