Contents
Changelog
Aug 1st, 2026
Announced: July 29, 2026
Aug 1st, 2026
The API v1 endpoints announced for deprecation in one of our previous changelog are now in an out-of-support state.
Although these endpoints may remain functional, Pipedrive no longer provides technical support, maintenance, bug fixes, or service-level guarantees for them. Their continued availability and behavior are not guaranteed, and they may be changed or removed without further notice.
What does “out of support” mean?
Integrations that continue to use the affected API v1 endpoints may still operate. However:
- Pipedrive does not guarantee their availability, reliability, performance, or response behavior.
- Issues affecting these endpoints may not be investigated or resolved.
- Fixes and improvements will be delivered only for the corresponding API v2 endpoints.
- These endpoints are not covered by Pipedrive’s standard service-level commitments.
For production integrations, continued use of out-of-support endpoints introduces a risk of unexpected disruption.
Who is affected?
This reminder applies to customers, partners, and Marketplace vendors whose integrations still use any of the API v1 endpoints included in the original deprecation announcement.
Deprecated endpoints:
| Deprecated API v1 endpoint | API v2 replacement |
|---|---|
| Activities | |
GET /v1/activities |
GET /api/v2/activities |
GET /v1/activities/collection |
GET /api/v2/activities |
GET /v1/activities/{id} |
GET /api/v2/activities/{id} |
POST /v1/activities |
POST /api/v2/activities |
PUT /v1/activities/{id} |
PATCH /api/v2/activities/{id} |
DELETE /v1/activities/{id} |
DELETE /api/v2/activities/{id} |
DELETE /v1/activities |
DELETE /api/v2/activities |
| Deals | |
GET /v1/deals |
GET /api/v2/deals |
GET /v1/deals/collection |
GET /api/v2/deals |
GET /v1/deals/{id} |
GET /api/v2/deals/{id} |
GET /v1/deals/search |
GET /api/v2/deals/search |
POST /v1/deals |
POST /api/v2/deals |
PUT /v1/deals/{id} |
PATCH /api/v2/deals/{id} |
DELETE /v1/deals/{id} |
DELETE /api/v2/deals/{id} |
DELETE /v1/deals |
DELETE /api/v2/deals |
GET /v1/deals/{id}/activities |
GET /api/v2/activities?deal_id={id} |
GET /v1/deals/{id}/persons |
GET /api/v2/persons?deal_id={id} |
GET /v1/deals/{id}/products |
GET /api/v2/deals/{id}/products |
| Persons | |
GET /v1/persons |
GET /api/v2/persons |
GET /v1/persons/collection |
GET /api/v2/persons |
GET /v1/persons/{id} |
GET /api/v2/persons/{id} |
GET /v1/persons/search |
GET /api/v2/persons/search |
POST /v1/persons |
POST /api/v2/persons |
PUT /v1/persons/{id} |
PATCH /api/v2/persons/{id} |
DELETE /v1/persons/{id} |
DELETE /api/v2/persons/{id} |
DELETE /v1/persons |
DELETE /api/v2/persons |
GET /v1/persons/{id}/deals |
GET /api/v2/deals?person_id={id} |
GET /v1/persons/{id}/activities |
GET /api/v2/activities?person_id={id} |
| Organizations | |
GET /v1/organizations |
GET /api/v2/organizations |
GET /v1/organizations/collection |
GET /api/v2/organizations |
GET /v1/organizations/{id} |
GET /api/v2/organizations/{id} |
GET /v1/organizations/search |
GET /api/v2/organizations/search |
POST /v1/organizations |
POST /api/v2/organizations |
PUT /v1/organizations/{id} |
PATCH /api/v2/organizations/{id} |
DELETE /v1/organizations/{id} |
DELETE /api/v2/organizations/{id} |
DELETE /v1/organizations |
DELETE /api/v2/organizations |
GET /v1/organizations/{id}/deals |
GET /api/v2/deals?org_id={id} |
GET /v1/organizations/{id}/activities |
GET /api/v2/activities?org_id={id} |
GET /v1/organizations/{id}/persons |
GET /api/v2/persons?org_id={id} |
| Products | |
GET /v1/products |
GET /api/v2/products |
GET /v1/products/{id} |
GET /api/v2/products/{id} |
GET /v1/products/search |
GET /api/v2/products/search |
POST /v1/products |
POST /api/v2/products |
PUT /v1/products/{id} |
PATCH /api/v2/products/{id} |
DELETE /v1/products/{id} |
DELETE /api/v2/products/{id} |
| Pipelines | |
GET /v1/pipelines |
GET /api/v2/pipelines |
GET /v1/pipelines/{id} |
GET /api/v2/pipelines/{id} |
POST /v1/pipelines |
POST /api/v2/pipelines |
PUT /v1/pipelines/{id} |
PATCH /api/v2/pipelines/{id} |
DELETE /v1/pipelines/{id} |
DELETE /api/v2/pipelines/{id} |
| Stages | |
GET /v1/stages |
GET /api/v2/stages |
GET /v1/stages/{id} |
GET /api/v2/stages/{id} |
POST /v1/stages |
POST /api/v2/stages |
PUT /v1/stages/{id} |
PATCH /api/v2/stages/{id} |
DELETE /v1/stages/{id} |
DELETE /api/v2/stages/{id} |
DELETE /v1/stages |
DELETE /api/v2/stages |
| Search | |
GET /v1/itemSearch |
GET /api/v2/itemSearch |
GET /v1/itemSearch/field |
GET /api/v2/itemSearch/field |
What should you do?
You should migrate all remaining usage of the affected API v1 endpoints to their API v2 equivalents as soon as possible.
API v2 provides:
- Better performance and consistency
- More efficient token consumption under Token-Based Rate Limiting
- Ongoing maintenance, fixes, and improvements
- Supported endpoints for production integrations
You can use the API Usage Dashboard in your company settings to identify whether your organization is still calling deprecated endpoints.
Marketplace vendors and integration partners should also review their applications to ensure they are not consuming customers’ token budgets through unsupported API v1 requests.
Important
The fact that an out-of-support endpoint remains accessible does not mean it is safe to continue using it.
Pipedrive does not guarantee an additional migration period before these endpoints are changed, restricted, or removed. To reduce the risk of integration failures, complete your migration to API v2 without delay.
If you work with a Pipedrive Partner or Customer Success contact, feel free to reach out for additional guidance or migration support.