# Pipedrive API tokens (/integrations/pipedrive-service-account)





Connect Pipedrive with an API token for one user in one company. The token uses that user's data access and remains valid until it is regenerated or the user loses access.

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 [#prerequisites]

In Sim, you need workspace write access and permission to manage integrations.

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.

<Callout type="warn">
  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.
</Callout>

## Finding the API token [#finding-the-api-token]

<Steps>
  <Step>
    In Pipedrive, click your profile picture in the top right, then **Personal preferences** → **API** — or go directly to `https://app.pipedrive.com/settings/api`
  </Step>

  <Step>
    Copy **Your personal API token** (generate one if the field is empty)
  </Step>
</Steps>

<Callout type="warn">
  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.
</Callout>

## Adding the API token to Sim [#adding-the-api-token-to-sim]

<Steps>
  <Step>
    Open **Integrations** from your workspace sidebar
  </Step>

  <Step>
    Search for "Pipedrive" and open it, then click **Add to Sim** and choose **Add API token**
  </Step>

  <Step>
    Paste the **API token**, and optionally set a display name and description
  </Step>

  <Step>
    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.
  </Step>
</Steps>

## Using the API token in workflows [#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. Choose the operation and configure its inputs.

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 [#rotating-the-token]

Pipedrive tokens don't expire on a schedule. To rotate one, regenerate it on the same **Personal preferences** → **API** 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.

## Verify feature access [#verify-feature-access]

Run a read action, then test the operations the workflow needs. The token uses its owner's access in one company and has no scopes to narrow it. A valid credential does not enable plan-restricted features such as Mailbox or Projects. If the issuing user is deactivated or loses company access, replace the token with one from an active account and update Sim.

See Pipedrive's [authentication](https://pipedrive.readme.io/docs/core-api-concepts-authentication) and [rate-limit reference](https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting). Search endpoints have their own burst limit, so the general API-token/OAuth comparison does not apply to every action.