We are excited to announce that a set of API v2 endpoints has officially moved out of BETA status and is now stable. These endpoints provide a more efficient and performant way to interact with Pipedrive, replacing specific APIv1 endpoints.

Why This Matters?

• Better Performance: API v2 endpoints are optimized for speed and reliability.
• Lower Token Costs: These endpoints consume fewer API tokens per request, making them a more cost-effective option.
• Improved Stability: As stable endpoints, they are fully supported and ready for production use.

Optimize API Usage with Token-Based Rate Limiting

Since the introduction of Token-Based Rate Limiting last year, we encourage all developers to migrate to available stable API v2 endpoints. Doing so will help you stay within your API token budget while maintaining seamless integration or even allow you to make more requests within the same budget.

What's Changing?

The following API v2 endpoints are now stable:

• GET /api/v2/activities
• GET /api/v2/activities/:id
• POST /api/v2/activities
• PATCH /api/v2/activities/:id
• DELETE /api/v2/activities/:id
• GET /api/v2/deals
• GET /api/v2/deals/:id
• POST /api/v2/deals
• PATCH /api/v2/deals/:id
• DELETE /api/v2/deals/:id
• GET /api/v2/persons
• GET /api/v2/persons/:id
• POST /api/v2/persons
• PATCH /api/v2/persons/:id
• DELETE /api/v2/persons/:id
• GET /api/v2/organizations
• GET /api/v2/organizations/:id
• POST /api/v2/organizations
• PATCH /api/v2/organizations/:id
• DELETE /api/v2/organizations/:id
• GET /api/v2/products
• GET /api/v2/products/:id
• POST /api/v2/products
• PATCH /api/v2/products/:id
• DELETE /api/v2/products/:id
• GET /api/v2/products/:id/variations
• GET /api/v2/products/variations
• POST /api/v2/products/:id/variations
• PATCH /api/v2/products/:id/variations/:id
• DELETE /api/v2/products/:id/variations/:id
• GET /api/v2/deals/:id/products
• GET /api/v2/deals/products
• POST /api/v2/persons/:id/products
• PATCH /api/v2/persons/:id/products
• DELETE /api/v2/persons/:id/products/:id
• GET /api/v2/itemSearch
• GET /api/v2/itemSearch/field
• GET /api/v2/deals/search
• GET /api/v2/leads/search
• GET /api/v2/persons/search
• GET /api/v2/organizations/search
• GET /api/v2/products/search
• GET /api/v2/pipelines
• GET /api/v2/pipelines/:id
• POST /api/v2/pipelines
• PATCH /api/v2/pipelines/:id
• DELETE /api/v2/pipelines/:id
• GET /api/v2/stages
• GET /api/v2/stages/:id
• POST /api/v2/stages
• PATCH /api/v2/stages/:id
• DELETE /api/v2/stages/:id

If you’re still using API v1 for these actions, we strongly recommend switching to API v2 to take advantage of its improved efficiency and reduced token consumption.

Additional resources:

• API Reference
• Developer documentation
• API usage optimization
• API v2 Migration Guide

If you have any questions or comments, feel free to let us know in the Developer’s Community.