APIs and integrations
HubSpot API Rate Limits: Burst, Daily and the Separate Search Cap
In short
HubSpot API rate limits hinge on how your app is distributed, so planning against the wrong row leaves a sync stalled by 429s. A marketplace OAuth app gets 110 requests per 10 seconds in each installing account. A private app gets 100 to 250 per 10 seconds plus a daily pool shared account-wide. CRM search sits apart at five a second.
Which HubSpot API rate limits apply to my app?
HubSpot's usage page splits apps by distribution, not by plan alone. Legacy public apps, and apps on developer platform versions 2025.2 and 2026.03 that use OAuth and are listed in the HubSpot marketplace, are held to 110 requests every 10 seconds for each account that installs them. That figure leaves out CRM search, which has its own ceiling.
The API limit increase add-on does nothing for that marketplace group. It only lifts privately distributed apps: legacy private apps and new-platform apps whose distribution is set to private. For those, the account's subscription tier sets two numbers at once, as below.
The page states no daily figure for marketplace OAuth apps. It describes only their 10-second allowance, so a daily budget for them is not something I would plan around from this source.
| Private-app tier | Per 10 seconds (each app) | Per day (whole account) |
|---|---|---|
| Free or Starter, any Hub | 100 | 250,000 |
| Professional, any Hub | 190 | 625,000 |
| Enterprise, any Hub | 190 | 1,000,000 |
| Any tier with the API Limit Increase | 250 | An extra 1,000,000 per increase, at most two increases |
Checked against: source 1
Why can one private app starve another of daily calls?
The burst column counts per app, but the daily column is one pool for every privately distributed app in the account. A nightly export written by one team can therefore exhaust the allowance a form sync depends on, even though the form sync never broke its own 10-second limit.
The daily counter resets at midnight in the time zone set on the HubSpot account, not at midnight UTC. For a worldwide team that matters when deciding when a heavy backfill should start.
Super Admins can see call usage in the account. For apps on the new developer platform it sits under Development, then Monitoring, then API call usage; legacy private apps keep a Logs tab on each app. A plain-language version of this problem for account owners lives at HubSpot API limit reached.
Checked against: source 1
How is CRM search throttled differently?
The CRM search endpoints are limited to five requests per second per account. That is a different window and a different counter from the 10-second allowance above, and search replies carry none of HubSpot's rate-limit headers. A client that paces itself only by those headers is blind on search and needs its own fixed pacing there.
Search also has shape limits that return 400 rather than 429: at most 200 objects per page, a request body of up to 3,000 characters, and no paging past 10,000 total results for one query. Filters max out at five filterGroups of up to six filters each, 18 in total.
Records created or changed a moment ago may not appear in results yet, and archived records never do. A create-then-search pattern can therefore miss the record it just wrote. HubSpot also flags the Associations and GraphQL APIs as having stricter limits of their own; this page does not cover them.
What does a 429 look like, and which headers can a client trust?
Once an app exceeds a limit, every following call gets 429 with a JSON body holding status, message, errorType set to RATE_LIMIT, correlationId, policyName and requestId. The policyName tells you which counter tripped: DAILY, or the rolling one the page calls TEN_SECONDLY_ROLLING.
HubSpot also caps failures: error responses should stay under 5% of total daily requests, and a marketplace app must stay under that share to be certified. Hammering a closed window therefore costs more than wasted calls.
The usage page does not promise a Retry-After header on API 429s. The error-handling page mentions one for 477 during a data-hosting migration, in seconds, and says workflows read it on 429 in milliseconds. I would pace from the headers below instead of waiting for a hint that may not come.
X-HubSpot-RateLimit-Interval-Milliseconds: the window length, for example 10000.X-HubSpot-RateLimit-MaxandX-HubSpot-RateLimit-Remaining: the allowance and what is left in that window.X-HubSpot-RateLimit-Dailyand-Daily-Remaining: absent on requests authorized with OAuth.X-HubSpot-RateLimit-Secondlyand its-Remainingpair: still sent, but deprecated, and the limit behind them is no longer enforced.
Do batch endpoints and caching actually cut the count?
HubSpot's own advice for repeated limit hits is to use batch APIs and cache what rarely changes, such as object properties, owners and form settings. Data shown on every page load should come from your cache, not a fresh API call each time.
Batch operations accept at most 100 records per request, so a 10,000-contact update is at least 100 calls. The contacts batch read cannot return associations; that takes a second call to the associations batch endpoint. Batch create can return 207 Multi-Status when multi-status error handling is enabled, which reports partial success instead of failing the whole set.
The pages read here do not spell out how one batch call is counted against the 10-second window. The guidance implies it beats single calls, but the exact counting rule is not written down.
Accounts with Marketing Hub Enterprise can push contact data out through workflow webhook actions, and those calls do not count toward the API limit.
Which other responses look like throttling but are not 429s?
HubSpot answers 502 or 504 when its processing limits are reached under a large, sustained volume, and 524 when nothing comes back within 100 seconds. Its stated remedy for each is a pause of a few seconds and a retry.
Some endpoints, including certain marketing single-send and source code calls, are exempt from the 10-second and daily counters. Their requests are not logged in HubSpot, and heavy use can still produce 5xx errors, which HubSpot says to treat like 429s.
What else do people ask?
Does buying the API limit increase help a marketplace app?
No. HubSpot states the add-on does not raise limits for legacy public apps or marketplace-distributed OAuth apps on the 2025.2 and 2026.03 platform versions.
When does the HubSpot daily limit reset?
At midnight in the time zone configured on the HubSpot account. The usage page also links an account-information endpoint that reports calls used so far today.
Sources
- HubSpot Developer Docs, API usage guidelines and limits, fetched 2026-11-20
- HubSpot Developer Docs, CRM search (Limits section), fetched 2026-11-20
- HubSpot Developer Docs, Contacts API guide (batch operations), fetched 2026-11-20
- HubSpot Developer Docs, Error handling, fetched 2026-11-20
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. This page reads HubSpot's own developer documents, fetched on 20 Nov 2026. I did not run a HubSpot app or send requests for it, so nothing here is a measurement. It does not cover the Associations, GraphQL, exports or forms limits, prices of the add-on, or any daily figure HubSpot leaves unstated. Found a mistake? Tell me.