The Pipedrive API rate limit has two layers. Each company gets a daily token allowance of 30,000 base tokens multiplied by a plan multiplier and the number of seats, plus burst limits per rolling 2-second window. When the daily allowance runs out, requests get a 429 error until the reset at midnight server time.
If your Pipedrive integration suddenly starts failing with 429 errors, it's almost always one of two limits: you've used the day's token allowance, or you've sent too many requests in a 2-second burst. They work differently and need different fixes, so it helps to know which one you've hit.
How the daily token allowance is worked out
Pipedrive charges tokens for each request rather than counting requests one for one. Every request consumes tokens from a daily allowance, and once it's exhausted, further requests are blocked until it resets the next day. The formula is:
30,000 base tokens x subscription plan multiplier x number of seats, plus any API token top-ups.
| Item | Limit | Applies to |
|---|---|---|
| Daily token multiplier | 1 | Lite plan |
| Daily token multiplier | 2 | Growth plan |
| Daily token multiplier | 5 | Premium plan |
| Daily token multiplier | 7 | Ultimate plan |
So a Growth account with 5 seats works out at 30,000 x 2 x 5, which is 300,000 tokens a day. The allowance is shared among all users in the company account, and it only covers API traffic using API tokens or OAuth tokens. Clicking around in the Pipedrive interface doesn't touch it.
What each type of request uses
| Request | Tokens |
|---|---|
| Get a single entity | 2 |
| Delete a single entity | 6 |
| Update a single entity | 10 |
| Delete a list of entities | 10 |
| Get a list of entities | 20 |
| Search for entities | 40 |
The pattern is clear: searches and list calls are the heavy ones. A sync that searches for every contact before updating it will burn through tokens far faster than one that fetches records by ID. API v2 endpoints are performance-optimised and charge fewer tokens than the original v1 endpoints, so moving to v2 is one of the easiest savings.
Burst limits per 2-second window
Separately from the daily allowance, burst limits apply per user on a rolling 2-second window, and they're counted per token, not per company.
| Item | Limit | Applies to |
|---|---|---|
| Burst limit, API token | 20 / 40 / 100 / 120 requests per 2 seconds | Lite / Growth / Premium / Ultimate |
| Burst limit, OAuth apps | 80 / 160 / 400 / 480 requests per 2 seconds | Lite / Growth / Premium / Ultimate |
| Search API burst limit | 10 requests per 2 seconds | All plans and authentication types |
Burst responses carry the headers x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset, so your code can slow down before it hits the wall. The x-daily-requests-left header applies only to api_token requests.
What happens when you hit the limit
Pipedrive's developer documentation sets out the sequence. Administrators get an email at 75% of the daily allowance and a second at 100%. After that, all requests are rejected with 429 until the reset. Integrations that keep sending high volume after getting 429 responses can also receive a 403 Cloudflare error page, which affects api_token integrations. Backing off when you see a 429 matters.
One noisy integration can lock out everyone
This is the part that causes the most trouble for small teams. Because the daily allowance is shared by every user in the company and scales with seat count, one badly behaved integration can use it up and lock out every other integration until midnight server time. And that reset may not match your local midnight, so an allowance that runs out mid-afternoon in London might not return until the next working morning.
If several tools talk to your Pipedrive account, check the API Usage Dashboard under Company Settings to see which one is using the most.
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.
Using fewer tokens
- Move to v2 endpoints, which charge fewer tokens than v1.
- Use webhooks instead of polling, so Pipedrive tells you about changes rather than you asking repeatedly.
- Cut back on search and list calls, the most token-heavy requests.
- Read the rate limit headers and pause before a burst limit trips.
Pipedrive also suggests restructuring the integration or moving to a higher plan. If the webhook idea is new to you, my explainer on the difference between an API and a webhook covers it in plain terms.
How other APIs compare
Asana's standard limit, as of Nov 2026, is 150 requests per minute on free domains and 1,500 on other domains, with search capped at 60 per minute. Calendly's API, per Zapier's help centre, allows 50 requests per token per minute on free plans and 500 on higher plans, including calls made through Zapier. If you're weighing up CRMs partly on integration headroom, see my Pipedrive alternatives.
My advice if your integration keeps hitting 429
Work out which limit you're hitting first: a burst limit clears in seconds, the daily allowance doesn't. Then check the API Usage Dashboard for the hungriest integration, move it to v2 endpoints and webhooks, and make sure it backs off on a 429 rather than hammering on. Most token problems come from searching where a direct fetch would do.
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 the Pipedrive API rate limit?
A daily token allowance (30,000 base tokens x plan multiplier x seats) plus burst limits per 2-second window.
What happens when I hit the limit?
Requests are rejected with a 429 until the allowance resets at midnight server time.
Does the limit count actions in the Pipedrive app?
No. It covers only API traffic authenticated by API tokens or OAuth tokens.
Is Search limited differently?
Yes. The Search API burst limit is 10 requests per 2 seconds on all plans.
How do I use fewer tokens?
Use v2 endpoints, webhooks instead of polling, and avoid heavy list and search calls.
