API Rate limits specify the number of requests a client can make to DatoCMS APIs in a specific time frame.
By default the Management API enforces rate limits of 60 requests per 3 seconds. Higher rate limits may apply depending on your current plan.
In the following list you can find all the headers returned in every response by the Content Management API which give a client information on rate limiting:
X-RateLimit-Limit: the maximum amount of requests which can be made in 3 seconds.
X-RateLimit-Remaining: the remaining amount of requests which can be made until the next 3-seconds reset.
X-RateLimit-Reset: if present, indicates the number of seconds until the next request can be made.
When a client gets rate limited, the API responds with the 429 Too Many Requests HTTP status code and sets the value X-RateLimit-Reset header to an integer larger than 0 specifying the time before the limit resets and another request will be accepted.
Our Ruby and JS API clients take care of rate limit errors and will automatically retry the request after the right amount of time.
For projects under a paid plan, even exceeding the API call or bandwidth limits does not lead to the interruption of the service, but the payment of an additional fee commensurate with the use. For projects under a free plan, service will be temporarily disabled until the beginning of the following calendar month, unless you provide a credit card. For more details, check our Plans, billing and pricing page.