To ensure fair usage and protect the stability of the Bokio API, rate limiting is implemented. Rate limiting restricts the number of requests that can be made within a certain time frame.
Current rate
Bokio API is rate limiting at 200 requests during a 60 seconds rolling window based on the provided bearer token.
Rate Limit Headers
When making requests to the Bokio API, you will receive the following headers related to rate limiting:
X-Bokio-RateLimit-Limit: The maximum number of requests allowed within the specified time frame.X-Bokio-RateLimit-Remaining: The number of requests remaining within the current time frame.X-Bokio-RateLimit-RetryAfter: The time until the rate limit will reset, represented in seconds left.
Handling Rate Limit Exceeded
If you exceed the rate limit, the API will respond with a 429 Too Many Requests status code. This indicates that you have reached the maximum number of requests allowed within the specified time frame.
To avoid this error, make sure to monitor the X-Bokio-RateLimit-Remaining header in the API response. If the remaining requests reach zero, you should wait until the X-Bokio-RateLimit-RetryAfter time before making additional requests.
It is recommended to implement proper error handling and back off strategies to handle rate limit exceeded scenarios gracefully.