Rate Limiting

All API endpoints are subject to rate limiting to ensure good performance for all customers. The rate limit is calculated per user. The default limit is:

1000 requests per 5 minutes
4 concurrent (parallel) requests

Limits can vary by plan, so check the Phrase pricing page for the concrete limits included in your plan. For your convenience we send information on the current rate limit within the response headers:

Header	Description
X-Rate-Limit-Limit	Number of max requests allowed in the current time period
X-Rate-Limit-Remaining	Number of remaining requests in the current time period
X-Rate-Limit-Reset	Timestamp of end of current time period as UNIX timestamp
X-Rate-Limit-Reason	Indicates which limit was exceeded (only present on `429` responses)

If you should run into the rate limit, you will receive the HTTP status code 429: Too many requests. The X-Rate-Limit-Reason header can have the following values:

Value	Description
global-rate	You exceeded your plan’s requests-per-5-minutes limit
global-concurrency	You exceeded your plan’s concurrent (parallel) requests limit

If you should need higher rate limits, contact us.

Conditional requests that return a 304 Not Modified response don’t count against your rate limits. See Conditional GET requests / HTTP Caching.

Overview

API Documentation