Skip to main content
To ensure high availability, stability, and fair usage for all our users, tipee’s API enforces rate limiting on all requests.

​
Overview

Rate limits specify the number of API requests a client can make within a certain period. If this limit is exceeded, subsequent requests will be temporarily blocked. We apply limits based on token bucket method.

​
Default Limits

Our rate limit is structured as follows :
  • Bucket : 500 requests
  • Re-fill rate : 4 tokens per second
It means that you have a pool up to 500 tokens at your disposal which fills up at a rate of 4 tokens per second. These limits apply to every endpoint available in documentation.

​
Checking Your Limit Status

We provide informations in the response headers of every API call. About your current rate limit status :
  • X-RateLimit-Limit : The maximum number of requests allowed in token pool.
  • X-RateLimit-Remaining : The number of requests remaining in the current window.
About the actual re-fill rate :
  • X-RateLimit-Rate-Amount: The number of seconds before you can make a request again.
  • X-RateLimit-Rate-Interval: The number of seconds before you can make a request again.
This allows you to proactively manage your request volume and avoid hitting the limit. Here is an example of one of the typical headers you will receive after a request : 
X-RateLimit-Limit: 500
X-RateLimit-Remaining: 456
X-RateLimit-Retry-After: 0
This allows you to proactively manage your request volume and avoid hitting the limit. We strongly recommend using these headers in your application to control your request frequency.

​
Exceeding the Limit

If you make too many requests in a short period and exceed your limit, the API will stop processing your requests and respond with an HTTP 429 Too Many Requests error code. We will include a Retry-After header indicating how many seconds you should wait before making another request : 
Retry-After: 1
You should not attempt to retry the request until this time has passed.