HexCon is coming to NYC. Catch the early-bird price before the time's up! Book me a spot

“Request was throttled. Expected available in 57.0 seconds.” error showing up.Solved

Participant
Discussion
2 years ago

I was trying to retrieve the battery level of my device using an api call but then this error“Request was throttled. Expected available in 57.0 seconds.” popped up. Initially it was possible to retrieve the battery level but after a few api calls, this error message was displayed. Does anyone know what triggers this error. Thanks in advance for the help.

Replies (2)

Marked SolutionPending Review
Hexnode Expert
2 years ago
Marked SolutionPending Review

Hey @am,
Welcome to the Hexnode community.

Hexnode UEM enforces rate limits for API requests to the Hexnode server to prevent server overloading and Denial of Service (DoS) attacks. API rate limits define the number of API requests made to the Hexnode server between set intervals.

API requests to the server exceeding the specified limit will be denied permission to access the required resource, also known as throttling. Only after the waiting period is over further API requests can be successfully made. Hexnode’s API rate limits are given below.

  1. 10 API calls per device in a day.
  2. 30 API calls in a minute.

If these API request limits are exceeded, the error messages “Request was throttled. Expected available in __ seconds.” or “Error 429: Too many requests” will be displayed. In your case, wait for the mentioned period before making further API requests.

Hope this answers your query.
Cheers!
Johan Blake
Hexnode UEM

Marked SolutionPending Review
Participant
2 years ago
Marked SolutionPending Review

Thanks for the info johan.