We are deprecating a set of legacy API v1 endpoints following the release of their more performant, efficient, and modern API v2 equivalents. This is part of our ongoing efforts to improve the reliability, scalability, and developer experience of our API platform.

What will change?

We are deprecating specific API v1 endpoints (listed below) that now have direct replacements in API v2 — this does not affect the entire API v1 platform. These API v2 endpoints offer improved performance and consume 50% fewer tokens under our Token-Based Rate Limiting system. Deprecated endpoints will remain accessible until December 31, 2025. After this date, their availability and functionality will no longer be guaranteed.

Deprecated endpoints:

Activities

• Deprecated GET /v1/activities in favor of GET /api/v2/activities
• Deprecated GET /v1/activities/collection in favor of GET /api/v2/activities
• Deprecated GET /v1/activities/{id} in favor of GET /api/v2/activities/{id}
• Deprecated POST /v1/activities in favor of POST /api/v2/activities
• Deprecated PUT /v1/activities/{id} in favor of PATCH /api/v2/activities/{id}
• Deprecated DELETE /v1/activities/{id} in favor of DELETE /api/v2/activities/{id}
• Deprecated DELETE /v1/activities in favor of DELETE /api/v2/activities/{id}

Deals

• Deprecated GET /v1/deals in favor of GET /api/v2/deals
• Deprecated GET /v1/deals/collection in favor of GET /api/v2/deals
• Deprecated GET /v1/deals/{id} in favor of GET /api/v2/deals/{id}
• Deprecated GET /v1/deals/search in favor of GET /api/v2/deals/search
• Deprecated POST /v1/deals in favor of POST /api/v2/deals
• Deprecated PUT /v1/deals/{id} in favor of PATCH /api/v2/deals
• Deprecated DELETE /v1/deals/{id} in favor of DELETE /api/v2/deals/{id}
• Deprecated DELETE /v1/deals in favor of DELETE /api/v2/deals/{id}
• Deprecated GET /v1/deals/{id}/activities in favor of GET /api/v2/activities?deal_id={id}
• Deprecated GET /v1/deals/{id}/persons in favor of GET /api/v2/persons?deal_id={id}
• Deprecated GET /v1/deals/{id}/products in favor of GET /api/v2/deals/{id}/products

Persons

• Deprecated GET /v1/persons in favor of GET /api/v2/persons
• Deprecated GET /v1/persons/collection in favor of GET /api/v2/persons
• Deprecated GET /v1/persons/{id} in favor of GET /api/v2/persons/{id}
• Deprecated GET /v1/persons/search in favor of GET /api/v2/persons/search
• Deprecated POST /v1/persons in favor of POST /api/v2/persons
• Deprecated PUT /v1/persons/{id} in favor of PATCH /api/v2/persons/{id}
• Deprecated DELETE /v1/persons/{id} in favor of DELETE /api/v2/persons/{id}
• Deprecated DELETE /v1/persons in favor of DELETE /api/v2/persons/{id}
• Deprecated GET /v1/persons/{id}/deals in favor of GET /api/v2/deals?person_id={id}
• Deprecated GET /v1/persons/{id}/activities in favor of GET /api/v2/activities?person_id={id}

Organizations

• Deprecated GET /v1/organizations in favor of GET /api/v2/organizations
• Deprecated GET /v1/organizations/collection in favor of GET /api/v2/organizations
• Deprecated GET /v1/organizations/{id} in favor of GET /api/v2/organizations/{id}
• Deprecated GET /v1/organizations/search in favor of GET /api/v2/organizations/search
• Deprecated POST /v1/organizations in favor of POST /api/v2/organizations
• Deprecated PUT /v1/organizations/{id} in favor of PATCH /api/v2/organizations/{id}
• Deprecated DELETE /v1/organizations/{id} in favor of DELETE /api/v2/organizations/{id}
• Deprecated DELETE /v1/organizations in favor of DELETE /api/v2/organizations/{id}
• Deprecated GET /v1/organizations/{id}/deals in favor of GET /api/v2/deals?org_id={id}
• Deprecated GET /v1/organizations/{id}/activities in favor of GET /api/v2/activities?org_id={id}
• Deprecated GET /v1/organizations/{id}/persons in favor of GET /api/v2/persons?org_id={id}

Products

• Deprecated GET /v1/products in favor of GET /api/v2/products
• Deprecated GET /v1/products/{id} in favor of GET /api/v2/products/{id}
• Deprecated GET /v1/products/search in favor of GET /api/v2/products/search
• Deprecated POST /v1/products in favor of POST /api/v2/products
• Deprecated PUT /v1/products/{id} in favor of PATCH /api/v2/products/{id}
• Deprecated DELETE /v1/products/{id} in favor of DELETE /api/v2/products/{id}

Pipelines

• Deprecated GET /v1/pipelines in favor of GET /api/v2/pipelines
• Deprecated GET /v1/pipelines/{id} in favor of GET /api/v2/pipelines/{id}
• Deprecated POST /v1/pipelines in favor of POST /api/v2/pipelines
• Deprecated PUT /v1/pipelines/{id} in favor of PATCH /api/v2/pipelines/{id}
• Deprecated DELETE /v1/pipelines/{id} in favor of DELETE /api/v2/pipelines/{id}

Stages

• Deprecated GET /v1/stages in favor of GET /api/v2/stages
• Deprecated GET /v1/stages/{id} in favor of GET /api/v2/stages/{id}
• Deprecated POST /v1/stages in favor of POST /api/v2/stages
• Deprecated PUT /v1/stages/{id} in favor of PATCH /api/v2/stages/{id}
• Deprecated DELETE /v1/stages/{id} in favor of DELETE /api/v2/stages/{id}
• Deprecated DELETE /v1/stages in favor of DELETE /api/v2/stages/{id}

Search

• Deprecated GET /v1/itemSearch in favor of GET /api/v2/itemSearch
• Deprecated GET /v1/itemSearch/field in favor of GET /api/v2/itemSearch/field

Why is it changing?

We’ve introduced API v2 as a faster, more consistent, and token-efficient evolution of our platform. These endpoints deliver enhanced performance, a better developer experience, and help reduce token consumption under Token Based Rate Limiting. By gradually deprecating older endpoints, we can focus our development efforts on continuing to improve and expand API v2.

Who is affected?

This change affects any customer, partner, or vendor currently using the deprecated API v1 endpoints.

What should you do?

No immediate action is required — your existing integrations using these endpoints will continue to work until the end of 2025.

To ensure a smooth transition:

• We recommend starting to migrate to API v2 equivalents as soon as possible to take full advantage of performance improvements and avoid future disruption.
• You can use the API Usage Dashboard in your company settings to identify if your organization is actively using any of the deprecated endpoints.
• A step-by-step API v2 Migration Guide is available to help your development team plan and implement changes.

If you work with a Pipedrive Partner or Customer Success contact, feel free to reach out for additional guidance or migration support.

When is it happening?

Deprecation takes effect as of today’s announcement. The affected API v1 endpoints will remain available until December 31, 2025, after which their availability and functionality will no longer be guaranteed.

Additional resources

• API v2 migration guide
• API reference
• Token based rate limiting