---
title: "HubSpot API rate limit calculator"
description: "HubSpot API rate limit calculator: pick your app type and tier, describe the job, and get the request count, run time, daily share and a safe throttle."
url: "https://jetstack.ai/tools/hubspot-api-rate-limit-calculator/"
---

Free tool

# HubSpot API rate limit calculator: requests, run time and a safe throttle

Choose your app type and HubSpot tier, then describe the job: the operation, how many records, batch or single, and how many workers. You get the number of requests, the minimum run time, the share of the daily limit, a safe throttle and a code snippet to paste.

Free, no sign-up. Data checked October 29, 2026.

Your app and account

App type Privately distributed app limits. HubSpot closed creation of new legacy private apps in September and October 2026; existing ones keep working.

HubSpot subscription The highest tier in the account.

API limit increases Private apps and service keys only.

The job

Operation

Number of records For associations, the number of record pairs.

Batch or single calls

Batch endpoint One call per record

Batch size Up to 100 for this endpoint.

Concurrent workers Threads or processes using the same app.

Requests other apps use per day Every privately distributed app in the account shares one daily limit. HubSpot's account information API reports today's call count, and private app responses carry `X-HubSpot-RateLimit-Daily-Remaining`.

Runs in your browser. Nothing you enter leaves this page. The safe throttle aims 10% under HubSpot's limit; HubSpot doesn't prescribe a margin.

### Your job

Fill in the job and press **Calculate**. Without JavaScript, work it out from the tables below: requests = records ÷ batch size, and the minimum run time in seconds = requests ÷ (the per-10-seconds limit ÷ 10).

Example: updating 50,000 records in batches of 100 on Professional is 500 requests; at 190 per 10 seconds that's at least 27 seconds, and 0.08% of the 625,000 daily limit.

## HubSpot API limits, checked October 29, 2026

From HubSpot's usage guidelines. These apply to legacy private apps, 2025.2 and 2026.03 apps with private distribution, and service keys. The burst limit applies to each app; the daily limit is shared by every app in the account and resets at midnight in the account's time zone.

| Subscription                           | Burst (per 10 seconds, per app) | Daily (per account)     |
| -------------------------------------- | ------------------------------- | ----------------------- |
| Free or Starter                        | 100                             | 250,000                 |
| Professional                           | 190                             | 625,000                 |
| Enterprise                             | 190                             | 1,000,000               |
| API limit increase (any tier, up to 2) | 250                             | +1,000,000 per increase |

### Limits that work differently

| API or app                                    | Limit                                                                                                                                                                                                                   |
| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Marketplace (publicly distributed) OAuth apps | 110 requests per 10 seconds per installing account, not counting CRM search. The limit increase doesn't apply. HubSpot doesn't publish a daily figure, and daily headers aren't sent for OAuth requests.                |
| CRM search                                    | 5 requests per second per account. Up to 200 results per page and 10,000 per query; 3,000 characters per request body; 5 filter groups of up to 6 filters, 18 filters in total. No rate limit headers in the response.  |
| Associations                                  | Free and Starter: 100 per 10 seconds. Professional and Enterprise: 150 per 10 seconds and 500,000 a day. With the limit increase: at most 200 per 10 seconds and 1,000,000 a day, however many increases you buy.       |
| Custom event completions                      | The send endpoint supports up to 1,250 requests per second; the batch endpoint takes batches of 500. 500 event definitions and 30 million completions a month per account.                                              |
| Exempt APIs                                   | Some APIs (for example marketing single send and some source code endpoints) don't count against the 10-second or daily limits. They aren't logged, and very high volume can return 5xx errors; handle those like 429s. |
| Large data syncs                              | A 423 Locked response means too much data in a short time (for example upserting thousands of companies). HubSpot advises a delay of at least 2 seconds between requests.                                               |
| GraphQL API                                   | Has its own limits; see HubSpot's GraphQL guide. Not modeled here.                                                                                                                                                      |
| Apps per account                              | 20 legacy private apps per account; 100 project-based apps, service keys and MCP connectors combined.                                                                                                                   |
| Webhooks                                      | 1,000 webhook subscriptions per app.                                                                                                                                                                                    |

### Batch sizes

| Operation                       | Max per request | Endpoint                                                                       |
| ------------------------------- | --------------- | ------------------------------------------------------------------------------ |
| Create records                  | 100             | `POST /crm/objects/2026-09/{objectType}/batch/create`                          |
| Update records                  | 100             | `POST /crm/objects/2026-09/{objectType}/batch/update`                          |
| Upsert records                  | 100             | `POST /crm/objects/2026-09/{objectType}/batch/upsert`                          |
| Read records by ID              | 100             | `POST /crm/objects/2026-09/{objectType}/batch/read`                            |
| Archive (delete) records        | 100             | `POST /crm/objects/2026-09/{objectType}/batch/archive`                         |
| Search records (CRM search API) | 200 per page    | `POST /crm/objects/2026-09/{objectType}/search`                                |
| Create associations             | 2,000           | `POST /crm/associations/2026-09/{fromObjectType}/{toObjectType}/batch/create`  |
| Read associations               | 1,000           | `POST /crm/associations/2026-09/{fromObjectType}/{toObjectType}/batch/read`    |
| Remove associations             | 100             | `POST /crm/associations/2026-09/{fromObjectType}/{toObjectType}/batch/archive` |

Association batch reads: HubSpot's current guide says 1,000 inputs, but a January 2025 changelog announced a cap of 100 IDs. If larger batches are rejected, use 100.

## How HubSpot counts your requests

HubSpot counts HTTP requests, not records. A batch update of 100 contacts is one request; updating the same 100 contacts one at a time is 100. Two counters run at once:

| Counter                       | Scope                                          | What it means for a job                                                                         |
| ----------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Burst** (per 10 seconds)    | Each app separately                            | How fast one integration can go. Adding workers to the same app doesn’t raise it.               |
| **Daily**                     | Every privately distributed app in the account | How much all your integrations can do together before midnight in the account’s time zone.      |
| **CRM search** (5 per second) | The whole account                              | Every app and worker that searches shares it, and search responses carry no rate limit headers. |

Marketplace apps get 110 requests per 10 seconds for each installing account instead, and the API limit increase doesn’t change that. The Associations API has its own, lower ceilings. Service keys follow the same limits as privately distributed apps. All of this is in the tables above and in our answer on [HubSpot API rate limits](https://jetstack.ai/answers/hubspot-api-rate-limits).

## Handling 429s and backing off

Once you’re over a limit, HubSpot returns `429` for every call until the window resets. The response body’s `policyName` tells you which limit you hit:

1. **Daily limit:** stop. Retrying burns error budget and nothing succeeds until midnight in the account’s time zone. Save your position and resume then.
2. **Burst limit:** wait, then retry with exponential backoff (for example 2, 4, 8 seconds, plus a little random jitter so workers don’t retry in lockstep). Give up after a few tries and log the record.
3. **`423 Locked`:** HubSpot returns this when you push a large volume of data in a short time. It advises a delay of at least 2 seconds between requests.
4. **`5xx` from exempt APIs:** handle them like 429s.

Read `X-HubSpot-RateLimit-Remaining` and `X-HubSpot-RateLimit-Daily-Remaining` on private app responses to slow down before you hit the wall. HubSpot asks you to keep error responses under 5% of your daily requests, and Marketplace certification requires it. Every retry is a request too, so a throttle that triggers constant 429s costs you twice.

## Batch or single calls

Batch endpoints take up to 100 records per request for CRM objects, so the same job uses up to 100 times fewer requests, finishes sooner and leaves daily budget for your other integrations. Use single calls when you need each record’s result straight away or the endpoint has no batch version. If a batch is rejected, split it to find the bad input rather than switching the whole job to single calls.

Search is a different trade-off. Pages of 200 sound efficient, but the account-wide limit of five searches per second, the 10,000-result ceiling per query and the short delay before new or updated records show up make search a poor engine for big syncs. If you can get the record IDs another way, batch read doesn’t compete with other apps’ searches and, on Professional and above, moves more records per second.

## Where Jetstack AI fits

Jetstack AI’s own API has separate limits per key: 5 requests per second and 100 per minute, reported in `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` headers, with `Retry-After` on a `429`. See [authentication and rate limits](https://jetstack.ai/docs/developers/authentication) and the [developer docs](https://jetstack.ai/docs/developers). For the credentials that set which HubSpot limits apply, see [HubSpot private apps and service keys](https://jetstack.ai/answers/hubspot-private-app), [creating properties through the API](https://jetstack.ai/answers/create-property-hubspot-api) and [auditing connected and private apps](https://jetstack.ai/answers/audit-connected-apps-private-apps-hubspot) (to find what else draws on your daily limit).

HubSpot API rate limit calculator

## Questions about this tool.

Do all my integrations share the HubSpot API limit?

Partly. For privately distributed apps (legacy private apps, private-distribution apps and service keys) the burst limit applies to each app separately, but the daily limit is shared by every app in the account. CRM search is limited to five requests per second per account, so every app that searches shares that too.

Does the API limit increase raise the limits for every app?

No. HubSpot says the increase raises only the privately distributed app limits, to 250 requests per 10 seconds and an extra 1,000,000 requests a day per increase, with at most two increases. It does not raise the 110 per 10 seconds for Marketplace apps, and the Associations API stops at 200 per 10 seconds and 1,000,000 a day however many increases you buy.

What should my code do when HubSpot returns a 429?

Read the policyName in the response body. If it says DAILY, stop: retries fail until the limit resets at midnight in the account's time zone. Otherwise wait, then retry with exponential backoff and a little random jitter. HubSpot asks you to keep error responses under 5% of your daily requests.

## Sources

- [API usage guidelines and limits (HubSpot Developers)](https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines)
- [CRM search guide (HubSpot Developers)](https://developers.hubspot.com/docs/api-reference/search/guide)
- [Using object APIs, 2026-09: batch limits and 423 responses (HubSpot Developers)](https://developers.hubspot.com/docs/api-reference/latest/crm/using-object-apis)
- [Associate records, 2026-09: association limits (HubSpot Developers)](https://developers.hubspot.com/docs/api-reference/latest/crm/associations/associate-records/guide)
- [Account service keys (HubSpot Developers)](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/account-service-keys)
- [Legacy private app creation sunset (HubSpot Developer Changelog)](https://developers.hubspot.com/changelog/legacy-private-app-creation-sunset)
- [Authentication and rate limits (Jetstack AI documentation)](https://jetstack.ai/docs/developers/authentication)

HubSpot changes often. Spotted something out of date? Tell us at <team@jetstack.ai>.
