About Rate Limit or RPS
API Rate Limit is a feature that limits the number of requests that a user or account can make to an API within a specific time period
Why Xendit Implement Rate Limit?
- To prevent any excessive or abusive use of an API
- To ensure that all customers have fair access to the resources provided by the API
How Much is The Limit of The API Request?
- In Test Mode, API Rate Limit is set 3000 requests per minute (RPM) for endpoint per account
- In Live Mode, API Rate Limit is set 6000 requests per minute (RPM) per endpoint per account
Below are the details of Rate Limit for your reference:
|Response Header||Value Example (Request per Minute)||Description|
|Rate-Limit-Limit||6000||Containing the requests quota in the time window|
|Rate-Limit-Remaining||5839||Containing the remaining requests quota in the current window|
|Rate-Limit-Reset||58.379||Containing the time remaining in the current window, specified in seconds|
If you exceed the rate limit for an endpoint, you will receive an HTTP status code of 429 (Too Many Requests) with the error code
It is important to handle this error and throttle your requests until the rate limit quota replenishes.
Best Practice to Handle Rate Limit
Here are some best practices for handling API Rate Limit gracefully as a client:
- Implement rate limiting in your application: As a client, it is important to implement rate limiting in your own application to ensure that you do not exceed the API's rate limits. This can be done by tracking the number of requests made and the time at which they were made, and comparing this to the API's rate limit policies.
- Handle rate limit errors: When you receive an HTTP status code of 429 (Too Many Requests) with the error code
RATE_LIMIT_EXCEEDED, it is important to handle this error gracefully in your application. One way to do this is to retry the request after a certain amount of time has passed, to give the rate limit quota a chance to replenish.
- Use exponential backoff: When retrying a request after a rate limit error, it can be helpful to use exponential backoff. This means that you should increase the amount of time you wait between retries by a factor of two (or some other multiplier) each time you receive a rate limit error. For example, you might retry the request after 1 second, then 2 seconds, then 4 seconds, and so on. This helps to reduce the risk of overwhelming the API with too many retries in a short period of time.
- Use caching: Caching the results of API requests can help to reduce the number of requests made to the API, and can also improve the performance of your application. By storing the results of API requests locally and reusing them until they become stale, you can reduce the need to make frequent requests to the API.
By following these best practices, you can help to ensure that your application handles rate limits gracefully and provides a reliable and consistent experience for your users.
We may reduce limits to prevent abuse, or increase limits to enable high-traffic applications. To increase the rate limit for your account, you can contact us 4 weeks in advance via email api.xendit.co by providing your Business ID. We will review your request and may be able to increase the limit based on the needs of your application and the overall usage of the API.
Further explanation about Xendit Rate Limit can be accessed here.