Content API Rate Limiting
As part of our security measure, we implemented API Rate Limiting which in effect would deny requests that are over the specified limit. Request rate-limiting is nothing new, it has always been a part of security and optimization. For security, it will help mitigate Brute Force Attacks, as well as DOS and DDOS attacks. This will also encourage users to optimize their side development-wise and make sure they are sending only consolidated requests where possible instead of multiple requests.
Default Values
Please check the table below for reference on the default rate limit per endpoint on Content API. These settings apply to all clients, if you feel a need to adjust the limit applied to you please contact your Account Manager.
Endpoint | Default Request Per Minute |
---|---|
GetChangeLog | 100 |
GetMyPropertyList | 200 |
PostProperties | 600 |
GetFacilities | 30 |
The limit resets per minute, you can retry the request at a later time in case you exceeded the limit.
If for whatever reason you want to know your current rate-limiting settings please don’t hesitate to contact us at techsupport@rakutentravelxchange.com.
Are We Exceeding Our Limit?
It is very easy to determine if your service is exceeding the rate limit. You would receive an HTTP Status Code of 429 Too Many Requests
, additionally, the body would be similar to the one below
{
"message": "API rate limit exceeded"
}
If you are seeing this error, please reduce the number of requests you are sending