Documentation is now available for the Fall 2020 Update release!

Throttling limits

Describes throttling limits for API server requests.

Leave Feedback

Introduction

API throttling limits the number of requests an API server accepts within a given time period. API requests are throttled to ensure a better quality of service.

If the number of API requests exceed the throttling limit, the following occurs:

  • The API request is rejected.
  • HTTP 429 Too Many Requests status code is returned. This indicates that too many requests were sent. within a given amount of time (“rate limiting”).

The following limits apply for each tenant (service provider, partner, and client) as requests per minute:

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

Usage information

API response headers include information on usage against throttling limits. This allows applications making API requests can self-regulate their requests.

HTTP HeaderDescriptionExample
X-RateLimit-LimitNumber of requests the user is allowed to make 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 at which the current rate limit window resets. Time in UTC epoch seconds.X-RateLimit-Reset: 1491397260

Error response sample

The following sample response is generated if the API requests exceed the rate limit:

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