HubSpot API
/v1/* version retirement
Stops workingSubscribe to HubSpot APIShare
Pipelines API V1 will shut down on December 4, 2026. This change impacts calls to /v1/* endpoints. After this date, these calls will fail as the API will no longer be supported.
Calls it hits
/v1/*
What to use instead of these calls
If your integration relies on V1 endpoints, migrate to the 2026-03 or later version.
In HubSpot API's words
HubSpot will sunset the Pipelines API V1 on December 4, 2026. After this date, the API will no longer be supported.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Version retirement
- Announced
- August 14, 2026
- Takes effect
- December 4, 2026
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against HubSpot API's own pages
Questions
When does this change take effect?
Calls to /v1/* on HubSpot API stop working on December 4, 2026.
What happens to calls after December 4, 2026?
They fail from that day.
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 HubSpot API 10
-
/crm/v3/extensions/accounting/*Removal Stopped working -
/extensions/ecomm/v2/*Removal Stopped working -
/calendar/v1/*Removal Stopped working -
GET /cms/v3/performance*Removal Stopped working -
/hubdb/api/v2/*Version retirement Stopped working -
/contacts/v1/lists*Version retirement Stopped working -
/crm-pipelines/v1/*Version retirement Stops workingin 28 days -
No date
/automation/v4/*Version retirement Deprecated, no date -
No date
/companies/v2/*Version retirement Deprecated, no date -
No date
/contacts/v1/*Version retirement 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 before December 4, 2026.