canonical: https://jentic.com/apis/pipedrive.com/pipedrive-api-v1

# Pipedrive API v1

Pipedrive API v1 provides programmatic access to developer tools functionality. The API exposes 213 endpoints.

## For AI agents

Programmatically get all activity fields, add new activity type. Covers 213 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get all activity fields
- Add new activity type
- Update an activity type
- Delete an activity type

## Use cases

### Developer Tools Operations

Use the Pipedrive API v1 to perform developer tools operations programmatically. The API provides 213 endpoints covering core functionality including get all activity fields, add new activity type, get all activity types.

Example prompt: Call GET /activityFields to get all activity fields

### Automated Activities Management

Automate activities operations by combining multiple Pipedrive API v1 endpoints. Agents can add new activity type and then get all activity types in a single workflow.

Example prompt: Call POST /activityTypes to add new activity type, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pipedrive API v1 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'get all activity fields', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /activityFields | Get all activity fields |
| POST | /activityTypes | Add new activity type |
| GET | /activityTypes | Get all activity types |
| PUT | /activityTypes/{id} | Update an activity type |
| DELETE | /activityTypes/{id} | Delete an activity type |
| GET | /billing/subscriptions/addons | Get all add-ons for a single company |
| POST | /callLogs | Add a call log |
| GET | /callLogs | Get all call logs assigned to a particular user |

## Key resources

- **Activities** — Activities are appointments/tasks/events on a calendar that can be associated with a deal, a lead, a
- **ActivityFields** — Activity fields represent different fields that an activity has.
- **ActivityTypes** — Activity types represent different kinds of activities that can be stored. Each activity type is pre
- **Billing** — Billing is responsible for handling your subscriptions, payments, plans and add-ons.
- **CallLogs** — Call logs describe the outcome of a phone call managed by an integrated provider. Since these logs a

## Why Jentic

- **Setup:** Wiring this Pipedrive v1 surface by hand means covering its many activity, call-log, and billing endpoints, paging through results, and handling retries yourself. Through Jentic you install once, import Pipedrive API v1 from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** You limit the agent to the operations it needs, such as reading activity fields or creating an activity type. Because you choose the allowed operations, deleting an activity type stays out of scope unless you add it.
- **Credential handling:** Your Pipedrive credential 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.
- **Discovery method:** Agents search Jentic by intent such as 'list activity fields' or 'create an activity type', and Jentic returns the matching Pipedrive API v1 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Pipedrive API v1 use?

The Pipedrive API v1 uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get all activity fields with the Pipedrive API v1?

Yes. Use the GET /activityFields endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pipedrive API v1?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get all activity fields through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get all activity fields'. Jentic returns the matching Pipedrive API v1 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Pipedrive API v1 have?

The Pipedrive API v1 exposes 213 endpoints covering activities, activityfields, activitytypes operations.

### Can I limit what my agent is allowed to do with the Pipedrive API v1?

Yes. Because you run Jentic One yourself, you decide which Pipedrive operations the agent may call and which stored credential it uses. You can allow read-only calls like getting activity fields (GET /activityFields) or getting all activity types (GET /activityTypes) while keeping write and destructive calls out of scope. Deleting an activity type (DELETE /activityTypes/{id}) or adding one (POST /activityTypes) stays blocked unless you explicitly add it to the agent's allowed operations.