Pipedrive API Documentation

Pipedrive's API Docs

Welcome to Pipedrive's Developer Documentation. Here you'll find comprehensive guides and documentation to help you start working with Pipedrive's API, as well as the Changelog to see any relevant changes regarding the public API.


All requests to our API need authentication.

If you're creating an app

then continue to OAuth 2.0 overview.
You can find our step-by-step guide to getting OAuth 2.0 implemented to your app in OAuth authorization .

If you're working with an API token integration

the API token must be provided as part of the query string for all requests, using the api_token variable, for example, https://companydomain.pipedrive.com/api/v1/deals/2?api_token=659c9fddb16335e48cc67114694b52074e812e03.

How to find the API token?

Keep in mind that an API token is tied to a specific user and company, giving access to all user's data. You can only have one active API token at any time. If you change the API token, all existing integrations using this API token will not be able to make successful requests against our API and stop working.

Updated about a year ago

Further reading

Custom fields


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.