Understanding the API Rate Limit and Cooldown Period at ControlUp

A user asked about the cooldown period for the API rate limit and received information from a colleague stating that there is a limit of 60 requests per user per minute or 200 per minute for the entire organization, with the cooldown period showing up in the header of the API query for retry attempts. The user was unsure if this applied to compliance APIs as well and was reassured that the limit is consistent across all APIs.

Read the entire ‘Understanding the API Rate Limit and Cooldown Period at ControlUp’ thread below:

Does anyone know how long the API rate-limit cooldown period takes? I’ve been building out a new automation and I think I have hit our rate limit as I keep getting an AxiosError reply.

I will check it out. Will get back to you

So I asked my colleague, and he mentioned the following: 60 requests per user per minute OR 200 per minute organization-wide, whichever is hit first. Cool down would be reported in the header from the API Query

This is what it would show up for the retry:

Let me know if this helps

Thank you, is this the same for the compliance APIs?

Should be the same across the board, let me know if you have a hard time finding it.

Continue reading and comment on the thread ‘Understanding the API Rate Limit and Cooldown Period at ControlUp’.  Not a member? Join Here!