Getting started
Rate limits
Each user can make up to 120 requests per minute, across all of their keys combined. The counter resets at the start of every clock minute.
Responses to a valid key show your usage in these headers:
| Name | Type | Description |
|---|---|---|
X-RateLimit-Limit | integer | Requests allowed per minute. |
X-RateLimit-Remaining | integer | How many are left in the current minute. |
X-RateLimit-Reset | integer | Seconds until the counter resets. |
Retry-After | integer | Only in the 429 response: seconds to wait before trying again. |
Above the limit, the response is 429 with the code rate_limited. Wait for the Retry-After time before trying again.
Attempts without a valid key (no key, a wrong key or a revoked key) are limited to 30 per minute for each IP address.
To stay under the limit
- Use
per_pageup to 100 to fetch more items with fewer requests. - To keep track of your TVs' status, one request per minute is enough.
- For large jobs, spread the requests over time and keep an eye on
X-RateLimit-Remaining.
Response headers200
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 117
X-RateLimit-Reset: 42Limit reached429
HTTP/1.1 429 Too Many Requests
Retry-After: 18
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 18
{
"error": {
"code": "rate_limited",
"message": "Too many requests. Try again in 18 seconds."
}
}