Pipedrive API
GET /v1/stages/{id} endpoint removal
Deprecated, no dateSubscribe to Pipedrive APIShare
Pipedrive API deprecated the GET /v1/stages/{id} endpoint without a shutdown date. This deprecation was announced on April 14, 2025. Once the removal takes effect, requests to this endpoint will fail.
Calls it hits
GET /v1/stages/{id}
What to use instead of these calls
Call GET /api/v2/stages/{id} instead.
In Pipedrive API's words
Deprecated GET /v1/stages/{id} in favor of GET /api/v2/stages/{id}
Facts
- API
- Pipedrive API
api.pipedrive.com - Kind
- Endpoint removal
- Announced
- April 14, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Pipedrive API's own pages
Questions
When does this change take effect?
Pipedrive API deprecated GET /v1/stages/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Pipedrive API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Pipedrive API 10
-
/v1/channels*Removal Stopped working -
No date
DELETE /v1/activitiesEndpoint removal Deprecated, no date -
No date
DELETE /v1/activities/{id}Endpoint removal Deprecated, no date -
No date
DELETE /v1/dealsEndpoint removal Deprecated, no date -
No date
DELETE /v1/deals/{id}Endpoint removal Deprecated, no date -
No date
DELETE /v1/organizationsEndpoint removal Deprecated, no date -
No date
DELETE /v1/organizations/{id}Endpoint removal Deprecated, no date -
No date
DELETE /v1/personsEndpoint removal Deprecated, no date -
No date
DELETE /v1/persons/{id}Endpoint removal Deprecated, no date -
No date
DELETE /v1/pipelines/{id}Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.