Rate Limiting
Our platform remains stable and fair for everyone by subjecting the APIs we provide to rate limiting and throttling. We ask developers to use industry-standard techniques for limiting calls, caching results, and re-trying requests.
If you exceed the rate limiting, your requests will be rejected with an error code of 429 Too Many Requests.
To avoid any disruptions caused by our rate limits, please contact us directly to discuss your specific needs.
Limits & Quotas
The rate limits are as follows, with each endpoint rate limited separately:
| Domain | Rate Limit |
|---|---|
| Authentication | 5 requests per minute per IP |
| Devices, Device Sources, Sites | 1 request per second per IP AND 1 request per second per user |
The rate limits are subject to change, and we will update this page with any changes.
Avoid Rate Limit Errors
Designing your application with best practices in mind is the best way to avoid throttling errors.
Consider the following best practices when designing your application:
- Most data returned in the API is static, so you can cache the data and only make requests when necessary.
- Use the
statusfor use-cases when you want to catch devices becoming offline or online.
If you have a specific use-case that requires a higher rate limit, we would like to hear about it, please contact us.