Pipedrive API Tokens

Pipedrive personal API tokens let your workflows authenticate to Pipedrive without a person's OAuth login. The token is issued per user per company, doesn't expire on its own, and stays valid until it's regenerated or the user is deactivated — no OAuth consent to renew.

The token carries the full data access of the Pipedrive user it belongs to, in that one company. For production workflows, create it from a dedicated Pipedrive user so a teammate leaving or regenerating their token doesn't break your automations.

Prerequisites

Any Pipedrive user with API access enabled can copy their token. If the API page is hidden, a Pipedrive admin may have disabled API access for non-admin users — an admin can enable it from the company's user settings.

Each user has exactly one active API token per company. Regenerating it immediately invalidates the old value everywhere it's used, with no grace period. If the token is shared with other integrations, coordinate before regenerating.

Finding the API Token

In Pipedrive, click your profile picture in the top right, then Personal preferencesAPI — or go directly to https://app.pipedrive.com/settings/api

Copy Your personal API token (generate one if the field is empty)

The API token grants everything its user can see and do in Pipedrive. Treat it like a password — do not commit it to source control or share it publicly. Sim encrypts the token at rest.

Adding the API Token to Sim

Open Integrations from your workspace sidebar

Search for "Pipedrive" and open it, then click Add to Sim and choose Add API token

Paste the API token, and optionally set a display name and description

Click Add API token. Sim verifies the token against Pipedrive (GET /v1/users/me) and names the credential after the Pipedrive user and company — if verification fails, you'll see a specific error explaining what went wrong.

Using the API Token in Workflows

Add a Pipedrive block to your workflow. In the credential dropdown, your Pipedrive API token appears alongside any OAuth credentials. Select it and configure the block as you normally would.

Sim sends the token in Pipedrive's x-api-token header (the documented scheme for personal API tokens), so every Pipedrive tool works unchanged.

Pipedrive gives API-token traffic lower burst rate limits than OAuth (roughly a quarter of the OAuth allowance, by plan), and every company shares one daily API budget across all users and both auth methods. Heavy workflow schedules can eat into the budget your other Pipedrive integrations use.

Rotating the Token

Pipedrive tokens don't expire on a schedule. To rotate one, regenerate it on the same Personal preferencesAPI page, then paste the new value into the credential in Sim right away — the old token stops working the moment a new one is generated.

Common Questions

The token doesn't depend on any user staying logged in or re-consenting, and it never expires on its own. Issued from a dedicated Pipedrive user, it's a stable credential for automated workflows.
Everything the Pipedrive user it belongs to can access, in that one company. There are no scopes to narrow it — pick the issuing user accordingly.
API tokens ignore scopes, but features like Mailbox and Projects still depend on your Pipedrive plan. A valid token doesn't unlock endpoints your plan doesn't include.
The token stops working immediately. Issue a new token from an active user (ideally a dedicated integration user) and update the credential in Sim.
Pipedrive gives API-token requests about a quarter of the OAuth burst allowance, and the company-wide daily API budget is shared across all users and integrations. Space out heavy schedules or switch busy workflows to OAuth credentials.

On this page