Rate limit in effect

We've always said we had a rate limit, but we never really enforced it. That has now changed.

AI is causing action

With the use of AI-agents, a lot more people are creating application and integrations with our API, and at a rapid pace. Which is great for the end user! Unfortunately though, AI agents don't seem that interested in optimizing. So we've seen some very unfortunate cases regarding the use of our API in recent months with high amounts of redundant requests and sometimes creating a lot of duplicate entries, leading to even more traffic to clean up after itself.

For that reason we're now actually enforcing our rate limit. For a start the rate limit is:

• 100 requests per minute per organization for our partners with ISV clients.

• 60 requests per minute per client for personal integrations.

This went into effect in the end of April and very few users were actually impacted, as expected. Only those with a lot of traffic even noticed. Now you might need to spread out requests a bit more at peak times, but nothing any integration with good intentions and optimized traffic can't handle to keep all of their existing functionality intact.

If you hit the rate limit you will get status 429. Do not retry over and over if you get this error, since you will just maintain your rate limit, instead wait a couple of seconds to recover. If you consistently keep running into the rate limit, consider adding a delay between requests to make sure you don't hit it.

For ISV partners, you also have the option to use our webhooks for entries and invoices, if you are running into the limit due to asking for these resources too quickly.

Here is a full overview of our status and error codes.

The future of the rate limit

Something we're already looking into is doubling the rate limit for night time traffic, since we have a lot of available resources at night anyway. This post will be updated if that takes effect.

In the future we might limit access further if neccessary to maintain high uptime and no disturbance to our end users in our interface, trying to move even more API traffic to the night time. We'll let you know before hand, if our limits change. This time we just started enforcing what has always been documented. :-D

Keep posted for more news.

Have a nice day. :-)