Rate Limits

Learn about API rate limits and how to work with them.

TPP API uses a number of safeguards against bursts of incoming traffic to help maximize its stability. Users who send many requests in quick succession might see error responses that show up as status code 429. We have several limiters in the API, including:

• A rate limiter that limits the number of requests received by the API within any given second.
• For most APIs, TPP allows up to 100 read operations per second and 100 write operations per second in live mode, and 25 operations per second for each in test mode.

A concurrency limiter that limits the number of requests that are active at any given time. Problems with this limiter are less common compared to the request rate limiter, but it’s more likely to result in resource-intensive, long-lived requests.

Treat these limits as maximums and don’t generate unnecessary load. Handling limiting gracefully for advice on handling 429s. If you suddenly see a rising number of rate limited requests, please contact support.

We may reduce limits to prevent abuse, or increase limits to enable high-traffic applications. To request an increased rate limit, please contact support. If you’re requesting a large increase, contact us 6 weeks in advance of when you’ll need the increased rate limit.