Pipedrive APIs for AI Agents
www.pipedrive.com·Developer portal → developers.pipedrive.com
Developer ToolsSource ControlDeal PipelineOfficial Vendor DocumentsNo authAPI keyAgent Ready
For Agents
APIs2 in catalogue
Endpoints248 indexed
AuthNo auth / API key
ProvenanceOfficial OpenAPI documents
An agent can create and move deals through pipeline stages, manage person and organization contacts, log calls and meetings as activities, capture and qualify leads, and register webhooks across Pipedrive's CRM APIs. It can also read and configure activity fields and activity types on the broader v1 surface.
Pipedrive API Catalog
2 APIs across 2 product groups.
Which Pipedrive API should I use?
| I want to... | Use |
|---|---|
| Create, move, and report on deals and manage person and organization contacts | Pipedrive API |
| Reach the full v1 reference including activity fields, activity types, call logs, and billing | Pipedrive API v1 |
Install Jentic One Beta
Connect the Pipedrive APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pipedrive APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpipedrive.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpipedrive.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “manage deals, contacts, and activities in Pipedrive CRM”.
What AI Agents Can Do with Pipedrive
Each workflow spans multiple Pipedrive APIs. Jentic routes each operation to the right API automatically.
End-to-end sales pipeline automation
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Pipedrive by hand means attaching your API token to every call, paging through deals, persons, and activities, and handling retries across two surfaces yourself. Through Jentic you install once, add Pipedrive from the Jentic API Directory, store the token once, and your agent calls both surfaces.
Permission scoping
You limit the agent to the operations it needs, such as creating a deal, adding a person, or logging an activity. Because your own rules choose the allowed operations, deleting an activity type or registering a webhook stays out of scope unless you add it.
Credential isolation
Your Pipedrive API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, including the query string.
Intent-based discovery
Agents search the Jentic directory by intent such as 'create a deal in Pipedrive' or 'add a person', and Jentic returns the matching Pipedrive operation with its input schema so the agent calls the right endpoint across either surface without browsing the reference docs.
FAQs
Specific to using Pipedrive APIs through Jentic.
What can an agent do across Pipedrive's APIs?
An agent can create and move deals through pipeline stages, manage person and organization contacts, capture and qualify leads, log calls, meetings, and tasks as activities, attach products for revenue tracking, and register webhooks for real-time events. On the broader v1 surface it can also read and configure activity fields and activity types and access billing and add-on information.
Do I need separate credentials for each Pipedrive API?
No. Both surfaces are Pipedrive REST APIs that authenticate with your per-user Pipedrive API token, so a single token covers the operations your plan allows across them. In Jentic you store that token once in your own Jentic One instance and it is reused for every Pipedrive operation you allow.
Which Pipedrive API should I start with?
Start with pipedrive-api for the everyday sales lifecycle: deals, persons, organizations, activities, leads, and webhooks. Reach for the broader v1 surface, pipedrive.readme.io, when you need configuration and account areas such as activity fields, activity types, call logs, or billing.
Can agents combine both surfaces in one workflow?
Yes. A common pattern is to configure activity types and fields on the v1 surface, then create deals and log activities of those types with the core surface. Because both use the same Pipedrive token, an agent can move between them without re-authenticating.
Are these Pipedrive APIs official?
Yes. Both surfaces are Pipedrive's own vendor-official APIs. They reflect Pipedrive's documented deal, contact, and activity model rather than any third-party reconstruction.
What is Pipedrive not suited for through these APIs?
These APIs cover sales pipeline, contact, and activity management. They are not built for email marketing, marketing automation, customer support ticketing, or accounting; pair Pipedrive with dedicated tools for those functions.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.