Introduction

API rate limits specify the number of requests an API server accepts within a given time interval. API requests exceeding the rate limit are throttled to ensure better quality of service. The request rate is in requests per minute.

If the number of API requests exceed the rate limit, the request is rejected with the following status:

HTTP 429 Too Many Requests

A 429 status code indicates that too many requests were made within the given time interval.

The following rate limits by API category apply to each service provider, partner, and client:

API CategoryGET (non-paginated)GET (paginated)POST/DELETE/PUT
Alerts50050200
Metric500505000
Device5005025
Tickets5005050
Other APIs5005050

Usage information

Using HTTP headers is recommended when making API requests because API rate limits can change due to performance and service considerations.

API response headers include rate limit information, permitting applications to self-regulate API requests.

HTTP HeaderDescriptionExample
X-RateLimit-LimitMaximum number of requests per minute.X-RateLimit-Limit: 500
X-RateLimit-RemainingNumber of requests remaining in the current rate limit window.X-RateLimit-Remaining: 14
X-RateLimit-ResetThe time when the current rate limit window resets, in UTC epoch seconds.X-RateLimit-Reset: 1491397260

Error response example

The following example response body is returned when the rate limit is exceeded:

{
	"error" : "throttled",
	"error_description" : "Too Many Requests"
}