API Throttling Limits

API Request Throttling

API throttling limits the number of requests an API server accepts within a time period. The API server rejects requests that exceed the limit and will return 429 Too Many Requests status code.

OpsRamp throttles API requests to ensure a better quality of service. The following limits apply for each tenant (service provider, partner, and client). API requests made after a throttling limit will fail with a 429 status code error.

Throttling Limits

API Category	GET (non-paginated) (requests/minute)	GET (paginated) (requests/minute)	POST/DELETE/PUT (requests/minute)
Alerts	500	50	200
Metric	500	50	5000
Device	500	50	25
Tickets	500	50	50
Other APIs	500	50	50

Note: The API rate limits may change to ensure better performance and service, hence it is advisable to use HTTP headers while making API requests.

API response headers include information on usage against throttling limits so that application making API request can self-regulate their requests.

HTTP Header	Description	Example
X-RateLimit-Limit	Number of requests the user is allowed to make per minute.	X-RateLimit-Limit: 500
X-RateLimit-Remaining	Number of requests remaining in the current rate limit window.	X-RateLimit-Remaining: 14
X-RateLimit-Reset	The time at which the current rate limit window resets. Time in UTC epoch seconds.	X-RateLimit-Reset: 1491397260

Sample Error Response

Below is the sample response generated if the API requests exceed the rate limit.

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