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.
Can the API rate limit be raised?
Your plan sets it. For the Support and Help Center API, per minute:
| Suite Team | 200 |
| Suite Growth and Suite Professional | 400 |
| Suite Enterprise | 700 |
| Suite Enterprise Plus | 2500 |
| Support Team, Professional, Enterprise | 200, 400, 700 |
Above that there is one route, the High Volume API add-on, which takes it to 2500. Note the row above it: on Enterprise Plus you already have that, so the add-on is not the answer to your problem.
What should I check before asking?
Open the API usage view in Admin Center. In most accounts that hit the limit, one consumer is responsible and it is fixable for nothing.
- A job fetching everything nightly that could fetch only what changed.
- One call per record where a bulk endpoint exists.
- Three scheduled jobs on the same minute that could be spread out.
- An app polling far more often than anything changes.
What a well-behaved integration does
Reads X-Rate-Limit-Remaining as it goes, and on a 429 Too Many Requests waits the number of seconds in the Retry-After header before trying again. One that treats 429 as a hard failure, 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
A request with that 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.