CRM API Rate Limits Compared, 2026: GoHighLevel, monday.com, Airtable and Pipedrive
Four CRMs, four different ways to cap an API. GoHighLevel allows 100 requests per 10 seconds and 200,000 a day per app. Airtable allows 5 a second per base. Pipedrive gives each company 30,000 tokens per seat per day times a plan multiplier. monday.com adds a daily call cap of 1,000, 10,000 or 25,000 by plan. The limits, checked October 17, 2026, and how long a 50,000-record sync takes on each.
Key takeaways
- GoHighLevel v2 allows 100 requests per 10 seconds and 200,000 requests a day per marketplace app per resource (location or company). Airtable allows 5 requests per second per base and 50 per second per user or service account.
- Pipedrive gives each company a daily budget of 30,000 tokens x a plan multiplier (Lite 1, Growth 2, Premium 5, Ultimate 7) x seats. A single-record update costs 10 tokens, a list call 20 and a search 40.
- monday.com has a daily call limit by plan: 1,000 on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise, resetting at midnight UTC. It also caps complexity points, minute rate, concurrency and IP traffic.
- Updating 50,000 records one request each takes about 83 minutes on GoHighLevel, 2.8 hours on Airtable, and 42 minutes on Pipedrive Growth. On monday.com it cannot finish in a day on any plan, because the daily call limit stops it first.
- The limits that stop a project are rarely the burst limits. They are the daily budgets, which are set by plan on monday.com and Pipedrive and by app on GoHighLevel.
Every CRM caps its API, and each one measures the cap differently. GoHighLevel counts requests per app, Airtable counts requests per base, Pipedrive spends a daily token budget, and monday.com stacks five separate limits on top of each other. This page puts the four side by side from each vendor’s own documentation, then runs the same job through all four: updating 50,000 records.
Checked on October 17, 2026 against HighLevel’s help center, Airtable’s developer documentation, Pipedrive’s developer documentation and monday.com’s API reference. Vendors change these numbers, so confirm before you size a project.
What are the API rate limits for each CRM?
| Limit | GoHighLevel | monday.com | Airtable | Pipedrive |
|---|---|---|---|---|
| Burst | 100 requests per 10 seconds per app per resource | Minute limit: 1,000 (other), 2,500 (Pro), 5,000 (Enterprise) queries per minute | 5 requests per second per base | 20 / 40 / 100 / 120 requests per 2 seconds per API token (Lite / Growth / Premium / Ultimate); OAuth apps 80 / 160 / 400 / 480 |
| Daily | 200,000 requests per app per resource | 1,000 (Free, Basic, Standard), 10,000 (Pro), 25,000 (Enterprise) calls | None stated | 30,000 tokens x plan multiplier x seats |
| Per user | Not stated | Not stated | 50 requests per second across personal access tokens | Burst is per token |
| Other caps | Basic API on Starter and Unlimited, advanced on Agency Pro | Complexity: 5M points per query; 5M a minute (app tokens), 10M combined (personal tokens); concurrency 40 / 100 / 250; IP 5,000 per 10 seconds | Plan tiering possible | Search: 10 requests per 2 seconds on every plan |
| On limit | Headers report usage | ComplexityException, DAILY_LIMIT_EXCEEDED, retry_in_seconds |
429, wait 30 seconds | 429 until budget resets |
Notes on reading the table:
- GoHighLevel applies the 100 per 10 seconds and 200,000 per day limits to public v2 APIs using OAuth, per Marketplace app and per resource, meaning a location or a company. v1 reached end of support on December 31, 2025, and new API keys can no longer be generated. Use a Private Integration token for single-account work. The help center also says basic API access comes with the Starter and Unlimited plans and advanced access with Agency Pro.
- monday.com tiers are named as in its API reference (Free, Basic, Standard, Pro, Enterprise). Marketplace apps and apps built by monday.com are excluded from the daily call limit. A rate-limit error costs only 0.1 calls. You can ask for a daily-limit increase from the API analytics dashboard.
- Airtable states the limits in one short page and reserves the right to change them or to tier them by plan.
- Pipedrive counts burst per token, not per company, and the daily budget is shared by every user in the account. UI actions do not draw on it.
How big is Pipedrive’s daily token budget?
Pipedrive’s formula is 30,000 base tokens x plan multiplier x seats. The multipliers are 1 for Lite, 2 for Growth, 5 for Premium and 7 for Ultimate. Tokens reset at midnight server time, which may not match your time zone.
| Seats | Lite | Growth | Premium | Ultimate |
|---|---|---|---|---|
| 5 | 150,000 | 300,000 | 750,000 | 1,050,000 |
| 10 | 300,000 | 600,000 | 1,500,000 | 2,100,000 |
| 25 | 750,000 | 1,500,000 | 3,750,000 | 5,250,000 |
Endpoint costs Pipedrive lists: get one entity 2 tokens, get a list 20, update one entity 10, delete one 6, delete a list 10, search 40. API v2 endpoints cost less than v1.
Worked example. A 10-seat team on Growth has 600,000 tokens a day. That covers 60,000 single-record updates (at 10 each), 30,000 list calls (at 20) or 15,000 searches (at 40). The same team on Lite has 300,000 tokens, so 30,000 updates. Administrators get an email at 75% and 100% of the budget. For the setup details, see the Pipedrive API integration guide.
How long does it take to update 50,000 records on each CRM?
The test: update 50,000 records, one record per request, at the vendor’s burst limit, and check whether the daily limit allows it. This assumes one request per record and no batching, so batching changes the result wherever the API supports it.
| CRM and plan | Burst speed | Time at burst speed | Daily limit allows it? |
|---|---|---|---|
| GoHighLevel, one location | 10 requests a second | 5,000 s, about 83 minutes | Yes: 50,000 of 200,000 |
| Airtable, one base | 5 requests a second | 10,000 s, about 2.8 hours | No daily cap stated |
| Pipedrive Growth, 10 seats, API token | 20 requests a second | 2,500 s, about 42 minutes | Yes: 500,000 of 600,000 tokens |
| Pipedrive Lite, 10 seats | 10 requests a second | 5,000 s, about 83 minutes | No: needs 500,000, budget is 300,000 (30,000 updates) |
| monday.com Pro | Up to 2,500 a minute (about 42 a second) | About 20 minutes | No: daily cap is 10,000 calls |
| monday.com Enterprise | Up to 5,000 a minute (about 83 a second) | About 10 minutes | No: daily cap is 25,000 calls |
Burst speeds come from each limit divided by its window: 100 per 10 seconds is 10 a second; Pipedrive’s 40 per 2 seconds on Growth is 20 a second and 20 per 2 seconds on Lite is 10. On monday.com, the complexity and concurrency limits may slow a real job further.
Two results stand out. First, monday.com’s burst speed is the highest but its daily cap is the lowest: at 10,000 calls a day on Pro, 50,000 one-record requests take five days, unless you batch several changes into each request, request an increase, or use a marketplace app, which the daily limit excludes. Second, Pipedrive’s limit depends on plan and seat count together, so the same job that fits on Growth with 10 seats fails on Lite.
Which limit usually stops a project?
The daily budget, not the burst rate. Burst limits make a job slow, and a good integration backs off and finishes. A daily budget makes a job stop for the day. That is why the question to ask before a migration is how many requests the job needs, set against each vendor’s daily number:
| If you plan to… | Check this first |
|---|---|
| Backfill tens of thousands of records into monday.com | Daily call limit for your plan, and whether you can batch |
| Sync a large table out of Airtable on a schedule | 5 requests a second per base, and the records-per-base cap |
| Run many integrations against one Pipedrive account | Seats x multiplier, since all users share one budget |
| Run many sub-accounts on GoHighLevel | The limit is per app per resource, so each location has its own 200,000 |
The GoHighLevel point is the unusual one. Because its limit is per app and per location, an agency that runs 40 sub-accounts through one app gets 40 separate daily quotas, where Pipedrive and monday.com give one shared pool per account. Read more in the GoHighLevel API integration guide and the monday CRM API integration guide.
What should you build into any CRM integration?
- Read the usage headers. GoHighLevel returns daily and burst remaining counts, Pipedrive returns burst headers and an API usage dashboard, and monday.com returns RateLimit headers and a complexity field.
- Retry with back-off, never from zero. monday.com returns
retry_in_secondsand Airtable wants a 30-second pause. Resume a failed bulk job from the last good record. - Prefer batch and v2 endpoints. Pipedrive’s v2 endpoints cost fewer tokens than v1, and fewer, larger requests protect every daily budget.
- Plan the backfill around the daily cap. For one-time loads, split the job over days or use an import tool, as described in CRM import limits.
If a migration or integration needs sizing against your plan, book a free 30-minute call and we will run the numbers with you.
Sources
- HighLevel help center, HighLevel API documentation, rate limits, v1 end of support and plan access, read October 17, 2026.
- monday.com developer documentation, Rate limits, read October 17, 2026.
- Airtable developer documentation, Rate limits, read October 17, 2026.
- Pipedrive developer documentation, Rate limiting, token budget, burst limits and endpoint costs, read October 17, 2026.