To ensure reliable performance and fair access for all customers, Arlo enforces rate limiting on all API endpoints. This article explains how rate limiting works, what to expect when limits are reached, and how to keep your integration running smoothly. For in-depth technical guidance and code examples, visit the Arlo developer documentation.
Rate limiting controls how many API requests can be made within a given time window. It is an industry-standard practice used to protect platform stability, prevent abuse, and ensure consistent performance across all customers.
- Arlo's API is limited to 300 requests per minute / 18,000 per hour
- This limit applies to all API endpoints available via the Arlo developer portal.
If your use case requires sustained usage above this threshold, please contact our support team to discuss your options.
When your integration exceeds 300 requests per minute, the API will return:
HTTP 429 – Too Many Requests
Your integration should be built to handle this response gracefully. See the recommendations section below.
For detailed guidance and code examples, refer to our API documentation.