Hexnode API returns 429 Too Many Requests when fetching device listSolved

Hey @rob_mitch,

The 429 response indicates that the API request rate has been temporarily throttled.

For Hexnode API requests, the current rate limit is 300 requests within a 10-minute window. This is not based on the laptop or server from which the API call is made. If the same API key or account is used from another machine while the limit window is still active, the requests can continue to return 429 until the window resets.

If you are fetching the device list from a custom web page, check whether the page is triggering repeated API calls in the background, for example through polling, retries, page refreshes, or multiple components calling the same endpoint. Even if only a few manual tests were performed, automated retries can quickly increase the request count.

Recommended approach:

1. Add request throttling or debouncing in the web application.
2. Avoid fetching the full device list repeatedly within a short period.
3. Cache the device list where possible and refresh it only when needed.
4. Add backoff logic when a 429 response is received.
5. Retry after the rate-limit window has passed.

There is currently no dashboard view that shows API usage count in real time.

Best Regards,
Isabel Lora
Hexnode UEM

We ran into something similar while building an internal tool. The issue wasn’t the number of devices, but how often our frontend refreshed the device list. Adding a short cache on our backend and limiting retries fixed the 429 errors for us.

Correct @shirleyc. Treat the 429 as a temporary rate-limit response. The practical fix is to reduce request frequency and implement retry handling with a delay instead of immediately retrying the same request multiple times.

Best Regards,
Isabel Lora
Hexnode UEM