Skip to main content

Hello,
I would like to make a suggestion regarding the rate limits.

The /accounts/ endpoint currently has a limit of 1 request per second and 15 requests per minute. In my opinion, the first of these two limits is unnecessary and creates additional difficulties for developers.

Often, when a user interacts with multiple windows or triggers several requests simultaneously, they quickly hit the per-second limit. This is problematic for two reasons:

  1. It requires more complex application logic, as well as retries, which ultimately only adds extra load to your system.

  2. In some cases, a client making 10 requests per minute can generate more load than one who makes 3 requests per second but then does nothing for the rest of the minute.

So, why not just keep the per-minute limit? Even if someone makes 15 requests in a single second, they wouldn’t be able to make any more for the rest of the minute anyway.

Thank you in advance for the explanation.

Hi ​@Supermetrics,

Thanks for the detailed explanation of why this endpoint can be tough to deal with. We want to make sure all our APIs are easy to use, so this is really useful to know. I just reached out to the product team and recommended to them that we update the rate limit in the future.