Help Scout's Inbox API allows up to 200 calls per minute on the Standard plan, 400 on Plus and 800 on the top tier, shared by every user on the account. Write requests and Search Conversations (v3) each count as 2 requests. Hit the limit and you'll get HTTP 429. The Free plan has no API access, as of Nov 2026.
One shared allowance per account
The first thing to know is who shares the limit. All users associated with the same account count against the same allowance. It isn't per user or per key, so your CRM sync, your reporting script and the agency's integration all draw from one pot.
| Item | Limit | Applies to |
|---|---|---|
| Standard plan | Up to 200 calls per minute | Account-wide; no reporting endpoints |
| Plus plan | Up to 400 calls per minute | Account-wide; all endpoints |
| Top tier | Up to 800 calls per minute | Account-wide; all endpoints |
| Write requests (POST, PUT, DELETE, PATCH) | Count as 2 requests | Every plan |
| Search Conversations (v3) | Counts as 2 requests | Every plan |
| Throttle response | HTTP 429 with X-RateLimit-Retry-After | When the limit is reached |
The Standard plan also has no access to the reporting endpoints, so if you want to pull reports through the API, you'll need Plus or the top tier. Help Scout says the Free plan doesn't include API access or integrations at all, as of Nov 2026.
Why your real allowance is lower
Help Scout Developers' page on rate limiting explains the detail that changes the maths. Write requests, meaning POST, PUT, DELETE and PATCH, count as 2 requests each. So does Search Conversations in v3. A bulk job that updates conversations gets roughly half the stated calls.
Here's how that works out on the Standard plan. With 200 calls a minute and every update counting as 2, a clean-up script can make about 100 updates a minute, and that's only if nothing else on the account is using the API at the same time. If an integration is searching conversations in the background, each of those searches spends 2 more.
The same logic applies on the higher tiers. On Plus, 400 calls a minute means about 200 v3 conversation searches a minute if searches are all you're doing. That sounds plenty until three tools are each searching on a timer. It's worth listing every app connected to the account and asking which of them needs to call the API that often.
Headers to read on every response
- X-RateLimit-Limit-Minute: the maximum number of requests per interval.
- X-RateLimit-Remaining-Minute: how many are left in the current interval.
- X-RateLimit-Retry-After: once you've hit the limit, how many seconds to wait.
When the throttle limit is reached, the API returns response code 429. Wait the number of seconds in X-RateLimit-Retry-After before trying again; retrying straight away just spends more of an allowance you don't have.
Planning a bulk job
- Check your plan's limit and whether you need reporting endpoints.
- Count writes and v3 searches as 2 when you estimate the job.
- Leave headroom for every other integration on the account.
- Pace the script using X-RateLimit-Remaining-Minute, and pause on 429 for the Retry-After time.
- Run big jobs outside working hours, when other tools are quieter.
If you're syncing changes from Help Scout into another tool, consider whether you need to poll at all. This explainer on APIs and webhooks covers the alternative.
What else the developer docs cover
Help Scout's developer docs cover the Inbox API, the Docs API for the knowledge base, Beacon JavaScript, apps and open source tools. The rate limit here applies to the Inbox API.
How two other help desks compare
Zendesk's High Volume API add-on raises a qualifying plan's limit to 2500 requests per minute for its Support and Help Center APIs. Intercom's private apps have a default limit of 10,000 API calls per minute per workspace, with 25,000 per minute per workspace across all apps. If API headroom is a deciding factor, my list of Help Scout alternatives and this round-up of Zendesk alternatives compare the platforms.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for integration builders
Treat the stated limit as shared and halve it for any job that writes. Read the remaining-calls header and slow down before you reach zero, and always honour X-RateLimit-Retry-After. If you're on the lowest tier and need reporting data, plan for Plus rather than trying to rebuild reports from other endpoints.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What is Help Scout's API rate limit?
200, 400 or 800 calls per minute, depending on the plan.
Does a POST count more?
Yes. Write requests count as 2.
What happens when I hit the limit?
You get HTTP 429, and the X-RateLimit-Retry-After header says how long to wait.
Is the API on the Free plan?
No, as of Nov 2026: Help Scout says Free has no API access.
Do all my users share the limit?
Yes. All users on the account share one limit.


