Pipedrive API review
Best CRM API for small sales teams
GET /api/v2/deals x-api-token: $PIPEDRIVE_TOKEN # get a list: 20 tokens. One record: 2. A search: 40. # Lite, one seat: 30,000 tokens a day # v2 endpoints cost fewer tokens than v1
The Pipedrive API is free in the sense that matters: no per-call charge, no credit balance, API access on every paid seat. What Pipedrive meters instead is complexity, through a daily token budget, and that model is unusual enough to be worth understanding before you write anything.
Every endpoint has a token cost. Reading one record costs 2 tokens, reading a list costs 20, updating a record costs 10, and searching costs 40. Your account gets a daily allowance calculated as 30,000 base tokens times a plan multiplier times your seat count, shared across everyone on the account. Spend it and every request returns 429 until midnight in Pipedrive's server timezone.
The practical effect is that Pipedrive charges you for the shape of your integration rather than its volume. A sync that reads records one at a time is cheap. A sync that searches for each one is twenty times more expensive for the same number of rows, and nothing in the invoice will tell you so.
Two things to settle early on any Pipedrive API integration. Decide between v1 and v2 before you write a client, because both are live and the v2 endpoints cost fewer tokens. And map your custom fields first: the Pipedrive API custom fields are returned under generated hash keys rather than the labels you see in the interface, so a response you have not mapped reads as nonsense.
The rest of the category is in the CRM and sync APIs listing.
What each operation costs in tokens
This is the whole cost model for the Pipedrive REST API, and it is published rather than inferred. Costs are per request, deducted from the company-wide daily budget.
| Operation | Tokens | At Lite with one seat | Notes |
|---|---|---|---|
| Get a single entity | 2 | 15,000 a day | One deal, one person, one organization. |
| Delete a single entity | 6 | 5,000 a day | |
| Update a single entity | 10 | 3,000 a day | The Pipedrive API create deal and update calls land here. |
| Delete a list of entities | 10 | 3,000 a day | |
| Get a list of entities | 20 | 1,500 a day | Paging through deals, leads or activities. |
| Search for entities | 40 | 750 a day | Twenty times the cost of a direct read. |
Pipedrive publishes a token cost on every endpoint in its API reference, so the six above are the shape rather than the whole list. The one that catches people is search at 40: a dedupe step that searches before every write turns a 3,000-row import into 150,000 tokens, which is five days of a single-seat Lite budget.
Those costs apply the same way across every entity. The Pipedrive deals API, the leads API, the activities API, persons, organizations, products, notes and files all follow the same verbs and the same prices, so reading a deal costs what reading a person costs. The Pipedrive email API and the webhooks sit slightly apart: email is its own resource rather than an activity type, and webhooks push to you instead of being polled, which is the cheapest way to stay in sync because it spends no tokens at all.
Pipedrive states that the API v2 endpoints are performance-optimized and therefore carry lower token costs than their v1 equivalents. Both versions are live and both have an OpenAPI 3 specification published. If you are starting now, start on v2; if you have a v1 integration that keeps hitting the budget, moving it is a real optimization rather than housekeeping.
Pipedrive API pricing, plan by plan
Pipedrive API pricing is seat pricing. There is no API line item, no credit pack and no metering in dollars, but the plan you buy multiplies your daily token budget, so the tier does change what the API can do.
Lite
- US$168 per seat per year
- Token multiplier 1, so 30,000 a day per seat
- Full API access
Growth
- US$468 per seat per year
- Token multiplier 2, so 60,000 a day per seat
- Email automation and follow-ups
Premium
- US$708 per seat per year
- Token multiplier 5, so 150,000 a day per seat
- Pipedrive marks this the most popular tier
Ultimate
- US$948 per seat per year
- Token multiplier 7, so 210,000 a day per seat
- The complete suite
Prices are the annual rate, which Pipedrive advertises as saving up to 42% against monthly. There is a 14-day trial with no card and no free tier after it. The multiplier is the part worth modeling: moving from Lite to Premium is four times the price and five times the token budget, so if the API is what you are buying, the expensive plan is cheaper per token.
A ten-seat Growth account gets 30,000 times 2 times 10, which is 600,000 tokens a day, and that is shared. One unattended integration can spend the whole thing before the sales team logs in, and nothing in the Pipedrive interface shows a rep why their search stopped working. Admins get an automated email at 75% and again at 100%, which is better than nothing and is not the same as a quota per integration.
One budget, shared, and it resets on their clock
Pipedrive API rate limits are a single daily number rather than a request rate, which is why the Pipedrive API limits page reads differently to every other provider here. The formula Pipedrive publishes is 30,000 base tokens times the plan multiplier times the number of seats, plus any API token top-ups you have bought.
| Plan | Multiplier | Daily tokens, 1 seat | Daily tokens, 10 seats | Searches a day, 10 seats |
|---|---|---|---|---|
| Lite | 1 | 30,000 | 300,000 | 7,500 |
| Growth | 2 | 60,000 | 600,000 | 15,000 |
| Premium | 5 | 150,000 | 1,500,000 | 37,500 |
| Ultimate | 7 | 210,000 | 2,100,000 | 52,500 |
What counts, and what does not
The budget covers API traffic only.
- Only requests authenticated by an API token or an OAuth token draw on it.
- Anything a human does in the Pipedrive interface is free and uncounted.
- The budget is per company account, shared across every user and every integration.
- Top-ups can be purchased and add to the daily figure.
When it runs out
Two warnings, then a hard stop.
- At 75% of the daily budget, an automated email goes to company administrators.
- At 100%, a second email, and every further request returns 429 Too Many Requests.
- Requests stay blocked until the budget resets.
- The reset is midnight in Pipedrive's server timezone, which may not be yours. Check before you schedule a nightly job.
This is the one CRM here where the integration design changes the cost more than the volume does. Reading 10,000 records one at a time is 20,000 tokens. Paging them 100 at a time is 2,000. Searching for each one is 400,000, which no plan below Premium can do in a day. Work out the token cost of your sync on paper first, because the failure mode is a 429 at 3am rather than a bigger invoice.
How to create a Pipedrive API key
The Pipedrive API is stateless and every request is validated against a token. There are two kinds, and the one you want depends on whether the integration is yours or something other companies install.
API token
The route for your own account.
- Found manually in the Pipedrive app, under your personal settings.
- Sent as the x-api-token header, or as a query parameter.
- Tied to a user, so it inherits that user's permissions.
- This is the Pipedrive API key people search for; Pipedrive calls it a token.
OAuth 2.0
For an app installed in accounts you do not own.
- Required for anything distributed through the Pipedrive marketplace.
- Draws on the installing company's token budget, not yours.
- Both kinds of token count against the same daily budget on the account they belong to.
An API token belongs to a user rather than to the account, so it can only see what that user can see, and it stops working when that user is deactivated. The usual failure is an integration built on a departing employee's token that breaks three months later for reasons nobody connects to the leaving date. Create a dedicated user for integrations, or use OAuth.
Where the Pipedrive API documentation lives
Pipedrive documents two live API versions side by side, with an OpenAPI 3 specification for each. The Pipedrive API documentation is split between a reference site and a developer portal, and the token costs live in the reference rather than the guides.
| Surface | Where | What it answers |
|---|---|---|
| API reference | developers.pipedrive.com/docs/api/v1 | Every endpoint, with its token cost. The Pipedrive API reference. |
| Developer docs | pipedrive.readme.io | Concepts, auth, rate limiting, migration guides. |
| OpenAPI v1 | developers.pipedrive.com/docs/api/v1/openapi.yaml | Generate a v1 client. |
| OpenAPI v2 | developers.pipedrive.com/docs/api/v1/openapi-v2.yaml | Generate a v2 client. Start here on a new build. |
| Rate limiting | pipedrive.readme.io/docs/core-api-concepts-rate-limiting | The token formula, the per-endpoint costs and the 429 behavior. |
| Status | status.pipedrive.com | Whether it is you or them. |
Pipedrive publishes client libraries, so a Pipedrive API Python or Node client is a dependency rather than a project, and supports importing either OpenAPI spec into Postman or Insomnia with a one-click Run in Postman button on the reference. It also warns that the spec files are updated occasionally and may need re-importing, which is a politer way of saying pin your generated client to a version.
Pipedrive also ships an MCP server, and it is on the MCP page with the others in this directory.
Pipedrive's own product walkthrough
Pipedrive publishes this on its own channel, so it is Pipedrive's account of Pipedrive, not ours. It is here because a rate card cannot show you the thing moving, and a minute or two of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.
YouTube · Pipedrive Welcome to Pipedrive! Onboarding Tour 1:06 · Published May 2022A one minute onboarding tour, which is as close to a product walkthrough as Pipedrive's channel gets. Nothing in it touches the daily token budget that actually decides what a Pipedrive integration costs, so the rate limits section above is the part to read.
Published 4 May 2022 on Pipedrive, the channel Pipedrive's own pages link to, and read on 13 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a Pipedrive page.
Strengths and limits
Pipedrive is the CRM that small sales teams actually run, and the API is built for that rather than for a platform play.
What it does well
- No metering in dollars: API access comes with every paid seat.
- Published token costs per endpoint, so the cost of an integration is calculable before you write it.
- Two live API versions with an OpenAPI 3 spec for each, and v2 costs fewer tokens.
- A Pipedrive MCP server, so an agent can reach the CRM without a client.
- US$14 a seat a month is the cheapest paid CRM in this directory.
- Admin warnings at 75% and 100% of the daily budget.
Where it falls short
- No free tier at all, only a 14-day trial.
- The daily budget is shared across every user and integration on the account.
- A search costs twenty times a read, which penalizes exactly the dedupe pattern most syncs use.
- The budget resets on Pipedrive's server clock, not yours.
- An API token is tied to a user and dies with that user.
- Lite at 30,000 tokens a seat is tight for anything more than a light sync.
Where Pipedrive data comes from, and what you may do with it
The question that arrives late and expensively is not how good the data is, it is who is allowed to hold it. These are the fields each one returns, the coverage it claims and the compliance it publishes.
| Provider | Fields returned | Coverage | Compliance | Redistribution |
|---|---|---|---|---|
| Pipedrive | CRM records, Work email, Firmographics | Global | GDPR DPA SOC 2 Type II | Not stated |
None of these states a redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first.
Two practical notes that apply to every provider on this page. A compliance badge describes the vendor, not your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And every one of these vendors runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs.
If Pipedrive is not the answer
Four providers in the CRM and sync APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.
HubSpot
Free tierA free tier including full API access, so you can build before paying. The obvious move if the missing free tier is what stopped you.
Attio
$44/user/moA schema you define through the API, with an SDK and MCP server alongside it, free to start and $44 a user after that.
Salesforce
US$125/seat/moThe step up when the org has outgrown a simple pipeline, with metadata and deployment APIs behind it. Price API access at US$125 a seat before committing.
Clay
$167/moNot a CRM. Worth naming because the Pipedrive limit people hit most is search, and search is usually enrichment wearing a CRM costume.
The full set, organized by the reason people leave, is on the Pipedrive alternatives page.
Pipedrive against the obvious rival
Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Pipedrive vs Salesforce, HubSpot vs Pipedrive, Attio vs Pipedrive and Pipedrive vs Zoho CRM.
Every pairing in the directory is on the compare hub.
Pipedrive vs Salesforce
CompareUS$14 a seat with the API included against US$125 a seat before the first call.
HubSpot vs Pipedrive
CompareA free tier with a per-second rate limit against a $14 seat with a daily token budget.
Attio vs Pipedrive
CompareA schema you define in code against a pipeline that works out of the box.
Before you build against it
Four things to settle first, each one read off Pipedrive's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.
Who should actually buy this
Buy Pipedrive when the sales team wants a CRM they can run without an administrator, and the integration work is modest. At US$14 a seat it is the cheapest paid CRM here, the API is included, and for a sync that reads and writes records directly the token budget will never bind.
Model the budget first if the integration is the point. The formula is public and the endpoint costs are public, so you can work out on paper whether your design fits before you buy a seat. If the answer is that it only fits on Premium, note that Premium is four times Lite's price for five times the tokens, which is the better deal per token and a worse one per seat.
Against HubSpot specifically, the trade is throughput model rather than feature list. HubSpot gives you API access on a genuinely free tier and limits you on requests per second. Pipedrive gives you no free tier and limits you on daily complexity. If you want to build before you buy, HubSpot. If you want a cheap seat for a team that will also use the CRM, Pipedrive.
A token budget rewards a well-shaped integration.
The difference between a sync that fits on Lite and one that needs Premium is usually a design decision nobody made deliberately. Frontal builds the sync to the budget, inside your account, and leaves you the arithmetic as well as the code.
Worked with 300+ companies. A senior operator runs your account.
What Pipedrive users say, in their own words
The one part of this page that is not a vendor claim. Quotes are transcribed as written and linked to the thread.
A third-party integration spends your token budget, and you find out late
[...] co-founder of Outfunnel. You're right that our Pipedrive API usage wasn't well optimized initially. At the time, we had no advance notice that API usage would become metered, and we were caught off guard by the change. Sorry if we burned through your limits during those first weeks! That said, we responded quickly once the issue became apparent, and since those initial hiccups, we've had no recurring problems with excessive or unnecessary API consumption.
r/pipedrive · June 2026 · 2 points
A vendor on the record about spending somebody else's allowance, which is the clearest illustration of what a shared daily budget means. Pipedrive's budget is 30,000 tokens times a plan multiplier times your seats, pooled across every integration on the account, so an app you installed from the marketplace draws on the same pool as the pipeline you wrote.
The practical note is the one the thread starts from: you will notice through a 429 on your own code rather than through a bill. Audit what is connected before you size a backfill, and check the marketplace apps first.
Ask for fewer fields before you buy more tokens
You can actually bypass this efficiency issue without buying their ridiculous $100 top-up package by switching your AI or integration to use Pipedrive's modern API v2 infrastructure. [...] v2 endpoints now support sparse filtering via a query parameter that lets you request only the exact keys you care about, shrinking a massive 2,000-character response down to a tiny snippet and drastically cutting down data over-fetching.
r/pipedrive · July 2026 · 5 points
The same lesson as the token costs in the table above, applied one level down. Pipedrive meters complexity rather than calls, so the lever is how much you ask for rather than how often. Requesting only the fields you use is the cheapest optimization available and it needs no plan change.
Treat the specifics as a pointer rather than as a published figure. Pipedrive's own API reference is the authority on which v2 endpoints accept a field selector and what each one costs in tokens, and that is the page to read before rewriting a client.
14 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page.
Pipedrive API, answered
Is the Pipedrive API free?
No. No free tier. 14-day trial, no card.
How much does the Pipedrive API cost?
Pipedrive starts at US$14/seat/mo. Billing is per seat and subscription. Read from Pipedrive's own pricing page on 8 October 2026.
What are the Pipedrive API rate limits?
Daily token budget: 30,000 x plan multiplier x seats. 429 when spent.
How do I get a Pipedrive API key?
API token from the app, or OAuth 2.0 for distributed apps. The current steps are in Pipedrive's own documentation, which is authoritative on anything that has changed since 8 October 2026.
Does Pipedrive have an MCP server?
Yes, at https://mcp.pipedrive.ai/mcp. It is listed with the others on the MCP page.