Skip to main content
Pipedrive

​
Overview

PropertyValue
Slugpipedrive
AuthOAuth 2.0 + PKCE
API versionv1
SandboxYes
Rate limit100 req/min, 10 req/sec

​
Supported resources

ResourceListGetCreateUpdateDelete
Contact✓✓✓✓✓
Lead✓✓✓✓✓
Deal✓✓✓✓✓
Meeting✓✓✓✓✓
Owner✓✓———
In Pipedrive, contacts map to Persons, and meetings map to Activities with type: meeting.

​
Connect setup

Pipedrive uses OAuth 2.0 with PKCE. You need an app from the Pipedrive Marketplace Developer Portal.
1

Create a Pipedrive marketplace app

Go to Pipedrive Developer Hub → Create app. Under OAuth & Access scopes, copy the Client ID and Client Secret.
2

Add the redirect URL

In your app’s Callback URL field, add:
http://localhost:5001/api/v1/auth/callback
3

Configure required scopes

Enable the following scopes:
  • contacts:read
  • contacts:write
  • leads:read
  • leads:write
  • deals:read
  • deals:write
  • activities:read
  • activities:write
  • users:read
4

Connect via the widget

When your end user opens the Connect widget, they enter the Client ID and Client Secret, then authorize via Pipedrive OAuth.

​
Usage

# List deals from Pipedrive
curl "http://localhost:5001/api/v1/deal?provider=pipedrive&endUserId=user-123" \
  -H "Authorization: Bearer sk_live_your_key"

# Update a meeting
curl -X PATCH "http://localhost:5001/api/v1/meeting/mtg-001?provider=pipedrive&endUserId=user-123" \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{ "title": "Q2 Review", "startTime": "2026-04-01T10:00:00Z" }'

​
Notes

  • Pipedrive uses cursor-based pagination with up to 500 records per page.
  • Owner details (name, email) are resolved via a secondary lookup on /v1/users/{id}.
  • Use environment: "sandbox" in your connect token to route requests to the Pipedrive sandbox.