Why Claude used up your Pipedrive API tokens (and how to avoid it)
If your AI changes Pipedrive through an integration, it spends your company's daily API token budget, and an AI that searches record by record, re-reads long lists or retries failed calls can spend thousands of tokens on a change that should cost under 100. This applies to community MCP servers, Zapier and the ChatGPT sync app; Pipedrive's official connector is "subject to token limits based on your plan", without saying whether that's the same budget. When the budget runs out, every integration gets a 429 error until the reset, which we measured at 07:00 UTC in October 2026.
Quick answer: what to do right now
| Your situation | What to do |
|---|---|
| Integrations are failing with 429 errors today | Stop the AI session. Requests stay blocked until the daily reset; see when the limit resets |
| You need more budget | There's no documented way to reset it early. Top-ups add 250,000 tokens each (up to 10), on Growth and higher plans; ask Pipedrive when they take effect |
| You want to see how much is used | Open Settings > Company > Usage in Pipedrive |
| You need to change one field on many records | Use Pipedrive's bulk edit in list view instead of the AI |
| You want your AI to keep doing the work | Give it record IDs or one filter, not one search per record. Prompts below |
| You run integrations that must not fail (web forms, syncs) | Keep AI bulk work small, and schedule big jobs right after the reset |
What happened on r/pipedrive
In July 2026 a Pipedrive user posted on r/pipedrive, under the title Pipedrive's API limits are ridiculous, that they had asked Claude to update one field on 38 people and ran out of the company's daily API budget. They wrote that Pipedrive "assessed over 450,000 API calls for this one task". They blamed searches that cost 40 tokens each and very large responses, and called the $100-a-month top-up they were offered absurd for one task. (We read the thread through a Reddit archive on October 29, 2026; the post doesn't say which Pipedrive connector Claude used.)
Changing a field on 38 records should be cheap. In our sandbox, updating one record with the v2 API cost about 2 tokens. The problem isn't the change. It's how the AI finds the records and what it does when something fails.
Where the tokens go
Pipedrive's rate limiting docs (updated September 17, 2026) list these costs: get one record 2, get a list 20, update one record 10, delete one 6, search 40. They also say v2 endpoints cost less, without numbers. We measured some v2 calls in a Pipedrive sandbox in October 2026:
| Call | Pipedrive docs | Measured in our sandbox (Oct 2026) |
|---|---|---|
| Search | 40 | Not measured |
| Get a list | 20 | 10 for 500 records (v2) |
| Update one record | 10 | About 2 (v2) |
| Get one record | 2 | About 2 |
| Merge two records | Not listed | 40 (v1) |
The official MCP can now also read email threads. Each list of a deal's or a thread's emails is a list call (20 in the docs), so "summarize every email with these 30 clients" adds up like any other loop.
Now the same 38-person change, done four ways. These are our estimates from the costs above, not a log of what happened in the Reddit case.
| How the AI does it | Approximate tokens |
|---|---|
| One filtered list of the 38 people, then 38 updates (measured v2 costs) | list (10) + 38 updates (76) = 86 |
| One search per person, then read and update each one (documented costs) | 38 searches (1,520) + 38 reads (76) + 38 updates (380) = 1,976 |
| Pages through all 10,000 contacts, 100 at a time, before each of the 38 changes (documented list cost) | 38 passes × 100 pages × 20 = 76,000, plus the updates |
| The same, but the AI retries each failed step once | 150,000 or more |
The gap between the first and third rows is the whole story: almost 900 times more tokens for the same result. An AI doesn't see the token cost of a call, so unless you tell it how to find the records, it may pick the expensive way. The 450,000 in the Reddit post is more than any row here, which fits a larger account read several times over with retries; we can't know what that agent did.
How big your budget is
The formula is 30,000 tokens × plan multiplier × number of seats, plus any top-ups (rate limiting docs). Pipedrive caps it at 100 million per company (usage limits).
| Plan | Multiplier | 1 seat | 3 seats | 10 seats |
|---|---|---|---|---|
| Lite | 1 | 30,000 | 90,000 | 300,000 |
| Growth | 2 | 60,000 | 180,000 | 600,000 |
| Premium | 5 | 150,000 | 450,000 | 1,500,000 |
| Ultimate | 7 | 210,000 | 630,000 | 2,100,000 |
The budget belongs to the company, not to each user. Your AI assistant, Zapier, your web forms, your email sync tools and anything else that uses an API token or OAuth share it.
What about Pipedrive's official MCP? Pipedrive says its MCP usage "is subject to token limits based on your plan and you can purchase additional tokens if needed" (MCP page). On October 29, 2026 it didn't say whether that's the same daily API budget or what each MCP action costs. For the ChatGPT sync app, Pipedrive does say the data it reads counts toward your API usage limits (ChatGPT Pipedrive app).
When the limit resets
Pipedrive's docs say the budget "resets at midnight at server's timezone", without saying which timezone. We measured it.
On October 16, 2026, we read the remaining budget every 3 minutes on our US-hosted sandbox account, with a 150,000-token budget (164 readings, no errors):
| Time (UTC) | Remaining / limit |
|---|---|
| 06:58 | 149,778 / 150,000 |
| 07:01 | 99,999 / 99,999 |
| 07:04 | 149,998 / 150,000 |
The reset happened at 07:00 UTC, which is midnight US Pacific daylight time. A first run the day before showed it had not reset at midnight UTC.
Three caveats:
- Clock change. The US goes back to standard time on November 1, 2026. If the reset follows Pacific time, it moves to 08:00 UTC. We will measure it again after that date.
- Other datacenters. Because the docs say midnight in the server's timezone, an account hosted in Pipedrive's EU datacenter probably resets at a different UTC hour. We measured only one account.
- The 99,999 reading. Around the reset we twice got 99,999 out of 99,999, which isn't the account's real limit. If a tool shows that number, wait a few minutes and check again.
What happens when it runs out
- Every API request fails with
429 Too Many Requestsuntil the reset. That includes integrations that have nothing to do with the AI: in March 2026 a developer described web form contacts failing to sync because of 429 errors. - Admins get warning emails. The API docs say at 75% and 100%; the usage limits article (updated October 12, 2026) says 80% and 100%.
- A job the AI was running stops halfway. Some records are changed and some aren't.
How to check and add budget in Pipedrive
See your usage: go to Settings > Company > Usage (usage limits).
Buy a top-up if you need one: go to Billing > Add-ons, turn on API tokens, click Review purchase and confirm. Each top-up adds 250,000 tokens, you can buy up to 10, and it needs the Growth plan or higher (top-ups, updated October 12, 2026). The article doesn't list a price; you see it at checkout.
For one field on many records, use bulk edit instead of the AI: in a list view, filter the records, select them and edit the field. It's a change made in Pipedrive's own interface, not by an API integration. Pipedrive's bulk edit guide warns that "Run automations" is on by default and, in its September 3, 2026 version, that changes can't be undone after you confirm. Pipedrive's product updates say that since March 2026 you can revert a bulk edit within 30 days from a page in Restore data (Tools and apps > Restore data). We haven't tested that revert yet (October 29, 2026), so export the records first.
Prompts that keep token use low
Copy these into Claude or ChatGPT before any change to many records:
| Prompt | Why it helps |
|---|---|
| "Find the records with one filtered list, not one search per record. If you can't filter, tell me and I'll give you the IDs." | One list instead of dozens of searches |
| "Before changing anything, tell me how many records match and show me the first 10. Then stop and wait for my OK." | Catches a wrong filter before it costs |
| "Here are the IDs of the 38 people: [paste IDs]. Update only these, one call each, and don't read anything else." | No searching at all |
| "If a call fails, stop and tell me. Don't retry more than once." | Stops retry loops |
| "Only return the fields name, owner and [field]. Don't fetch notes, emails or activities." | Smaller responses, fewer follow-up reads |
You can get the IDs yourself: filter the list in Pipedrive and export it, then paste the ID column into the chat.
Before you run a big AI job
- Check today's usage in Settings > Company > Usage.
- Start right after the reset, so a mistake doesn't block your forms and syncs for the whole day.
- Give the AI IDs or one filter, not names to search.
- Ask for a count and a sample before any write.
- Tell it to stop on the first failure.
- Do the math for your plan: with documented costs, a search, read and update per record is about 52 tokens, so a 1-seat Lite account (30,000 a day) runs out at about 570 records. Keep each run well under that.
Where Pipehand fits
Pipehand is planned to launch in April 2027 as a replacement for Pipedrive's MCP, with a different approach to the budget. Your AI's reads will come from a synced copy of your Pipedrive data, so they won't spend API tokens unless the AI asks for fresh data. Emails and projects are the exception: Pipehand is designed not to keep a copy of your emails, so reading them will spend tokens like any live call. It will read the remaining budget on every call, let you cap how much of the daily budget it can use, and spread large merges and bulk edits across days so your other integrations keep working. Every change will have an undo, and merges and bulk edits a preview.
If an AI has burned your Pipedrive API budget, join the waitlist on pipehand.com.
FAQ
Does Claude use Pipedrive API tokens?
Claude itself doesn't, but the connector it uses can. Community MCP servers and Zapier call Pipedrive's API and spend your company's daily budget. Pipedrive's official MCP is "subject to token limits based on your plan"; Pipedrive doesn't publish its cost per action.
When does the Pipedrive API limit reset?
Pipedrive's docs say midnight in the server's timezone. We measured 07:00 UTC on October 16, 2026, on a US-hosted account, which is midnight US Pacific daylight time. It may move to 08:00 UTC after November 1, 2026, and EU-hosted accounts likely reset at another hour.
What does a 429 error from Pipedrive mean?
It means too many requests. Either the daily token budget is used up, and requests fail until the reset, or a short burst limit was hit, which clears within seconds. If every integration fails at once and keeps failing, it's the daily budget.
How many tokens does a Pipedrive API call cost?
Pipedrive documents 2 to read one record, 20 for a list, 10 to update, 6 to delete and 40 to search. In our sandbox in October 2026, a v2 list of 500 records cost 10, a v2 update about 2, and a merge 40.
Can I buy more Pipedrive API tokens?
Yes. In Billing > Add-ons you can add API token top-ups of 250,000 each, up to 10, on the Growth plan or higher. The total is capped at 100 million per company. Pipedrive's article doesn't list the price.
How many API tokens does my Pipedrive plan include?
30,000 per seat per day on Lite, 60,000 on Growth, 150,000 on Premium and 210,000 on Ultimate, shared by the whole company.
For developers
Headers, burst limits and measured costs
- Headers: every response carries
x-daily-ratelimit-token-limitandx-daily-ratelimit-token-remaining. There's no header with the daily reset time (x-ratelimit-resetis for the 2-second burst window). We measured the reset by readingGET /v1/users/me(2 tokens) every 3 minutes. - The placeholder value: treat
99999 / 99999as unknown, not as a reset or as an empty budget. - Burst limits (rolling 2-second window, from the docs): Lite 20, Growth 40, Premium 100, Ultimate 120 with an API token; 80, 160, 400 and 480 with OAuth. Search is 10 per 2 seconds on every plan. We measured 20 with an API token and 80 with OAuth on the same account; the daily budget was the same for both. The docs add that clients that keep sending requests after a 429 may get a 403 instead.
- Cheaper patterns: use v2 list endpoints with filters instead of search, request up to 500 per page, cache what you read, and use webhooks instead of polling, as Pipedrive's optimization guide recommends.
- Scale check (estimated from our measured unit costs): listing 10,000 people, 10,000 organizations and 10,000 deals with v2 would cost about 600 tokens. 1,000 merges would cost about 40,000, more than a one-seat Lite account gets in a day.