Plan requirement
| Subscription | Any plan |
| Access | Admin |
Sometimes, and it is worth finding out what is consuming your current allowance first, because one consumer is usually responsible.
The limit depends on your plan
Higher plans get more calls per minute. So the first question is whether you are on the plan you need for other reasons anyway.
Look before you ask
Open the API usage view in Admin Center. In most accounts that hit the limit, one consumer is responsible, and it is usually fixable for free.
- A job fetching everything nightly that could fetch only what changed.
- One call per record where a bulk endpoint exists.
- Three scheduled jobs at the same minute that could be spread out.
- An app polling far more often than anything changes.
What a well-behaved integration does
Reads the rate limit response, waits, and retries. One that treats it as a hard error, or retries immediately, turns a brief limit into a sustained one.
If you built the integration, that is worth checking. If a supplier did, it is worth asking them.
Then ask
Having done the above, a request with evidence behind it is a different conversation from one that starts with the limit being inconvenient.
Not sure what is using your allowance? Send us what you see and we will help you work out which consumer to look at first.
Comments
0 comments
Article is closed for comments.