Hexnode API returns 429 Too Many Requests: quota and rate limit explainedSolved

Hi @eduardo, 

The 429 Too Many Requests response is returned when the Hexnode API request limits are exceeded. 

Here is exactly how the Hexnode API limits are structured and calculated: 

• Daily API limit: 10 API calls per day, per managed device. 
• Account-level daily allowance: This is calculated as your total managed devices × 10 calls. 
• Minute-level rate limit: 30 API calls per minute. 

For example, if your account has 100 managed devices, your account-level daily allowance would be 1,000 API calls. If either your total daily allowance or the 30 calls-per-minute threshold is exceeded, subsequent API requests will return the 429 Too Many Requests error. To avoid encountering this, it is recommended to space out your API requests and implement a retry mechanism within your integration. 

Please let me know if you would like an example of how the minute-level threshold triggers! 

Best regards,
Eden Pierce,
Hexnode UEM 

Does the 10 calls per device limit have to be distributed evenly? for example, if I make 20 API calls for one device and none for another, would that still be allowed as long as the total account limit is not crossed?

Hi @eduardo, 

The calls do not need to be evenly distributed across your devices. While the daily allowance itself is calculated from the total number of managed devices you have, the actual API calls can be distributed and used across those devices however you see fit. 

Therefore, making more calls for a single device and fewer or zero calls for another is completely acceptable, provided that your total account-level daily API allowance is not exceeded and your integration does not cross the 30 calls-per-minute rate limit. 

Setting up a throttling mechanism alongside your retry strategy will ensure your account wide allowance is distributed smoothly throughout the day. 

Cheers,
Eden Pierce,
Hexnode UEM