Pipedrive API Guide for Contractors

One-line verdict: Deals and people connect on day one with a simple token — but project work needs the Projects add-on, and every call spends from a daily token budget set by your plan and your seats. Openness: 4 / 5 — rated 4 because Pipedrive documents a REST API with two sign-in routes and a webhook system, held back from 5 by the Marketplace approval for public apps, the add-on gate on Projects, and the metered budget.

The connection that works

Rung 1 — Direct connection. Pipedrive’s REST API (v2 is the current surface — v2 endpoints are stable, and v1 endpoints with v2 replacements were deprecated from January 1, 2026) offers the two sign-in patterns this directory likes to see separated: a personal API token for your own account — Pipedrive’s own tutorials create a deal with nothing but “your API token and company domain” — and OAuth 2.0 for apps headed to the Marketplace, with per-app permission scopes.

Verified: Persons (Pipedrive’s contacts) — read and create; Deals — read and create (the tutorial’s one compulsory field is the title, which tells you how low the floor is); Projects — read verified, with the Projects API’s launch post describing create/manage and two OAuth scopes — behind a gate stated in the same breath: “the endpoints are tied with the Projects add-on which has to be enabled.” Project Templates are read-only. Organizations ride the same reference family; their per-endpoint verbs weren’t separately extracted in our pass and are flagged below.

Webhooks: documented, created through the API by event action and object (create.deal, or wildcards), permission-checked against the webhook owner’s access. Current version discipline matters here: Webhooks v2 became the default on March 17, 2025, adding lead, project, and deal-product events, and v1 webhooks “will be deprecated completely in 2026” per the vendor. Build on v2.

The meter: since December 2024, requests consume tokens from your company’s daily budget, resetting every 24 hours; exceed it and the API returns 429 until tomorrow. v2 endpoints consume fewer tokens — the deprecated v1 set costs about 50% more — which is a practical reason, beyond support, to build on v2. The exact budget formula (base × plan multiplier × seats) appears in bridge and third-party sources, not in the vendor text we extracted, so the mechanism is published here and the formula stays UNVERIFIED as a vendor figure.

Bridge apps: both bridges are real — Zapier lists deal/person/activity triggers and actions, and Make lists a Pipedrive CRM app with watch-deals triggers and rich actions (bridge evidence). On a token-simple API like this, bridges are convenience, not necessity.

Can automate

• Speed-to-Lead — a person and a deal can be created from any intake source with one token; follow-up keys off real pipeline records.
• Pipeline hygiene — deals are readable and creatable, webhooks fire on create/update, so stage discipline can be enforced by software instead of reminders.
• Project handoff — with the add-on — won deals can become Projects records your delivery side works from, once the Projects add-on is enabled.
• Products on deals — deal line items with price and quantity are documented, so deal value can be built item by item from another system.

Can’t automate

• Customer invoices or payments — no objects exist. The reference’s Billing section is Pipedrive billing you (your subscription, plans, add-ons) — not an invoicing API for your customers. Any “Pipedrive invoices API” claim is a misread.
• Estimates or quotes as documents — UNVERIFIED. No quotes/estimates endpoint appears in the reference families checked. A product attached to a deal is a line item, not a quote document.
• Projects without the add-on — the endpoints refuse without it, per the vendor’s own launch post.
• Yesterday’s surfaces — deprecated v1 endpoints (availability not guaranteed after December 31, 2025) and v1 webhooks (full deprecation in 2026) are not buildable ground.
• Organization verbs, one by one — UNVERIFIED in this pass beyond the reference-family listing.

Hidden gate: Deals connect on day one with a simple token — but project work only connects if you bought the Projects add-on, and every call spends from a daily token budget set by your plan and your seats. A small plan’s budget is a real ceiling, not a footnote.

Build fit — what this platform supports well

• Speed-to-Lead — strong fit: the lowest-friction create path in this directory.
• Estimate Follow-Up — partial: follow-up keys off deal stage and value; the quote document itself lives in your estimating tool, because Pipedrive has no quote object.
• Invoice Chase / AR — not here: no invoice or payment objects. The chase runs against your accounting system; Pipedrive supplies the won-deal signal.
• Review Engine — like every platform here, Pipedrive has no verified reviews API, so the review ask runs on our system triggered by a job-completion signal — a won deal or a completed project can supply it.

What this means for your shop

If your shop sells out of Pipedrive — common for sales-driven remodelers and specialty contractors — the pipeline is genuinely open: cheap to connect, honest to meter. Keep three disciplines: build on API v2 and Webhooks v2 only, enable the Projects add-on before promising a deal-to-project handoff, and count your daily token budget like you’d count a crew’s hours — because when it runs out, every connected tool stops until midnight.