HubSpot API
/crm/v3/* version retirement
Deprecated, no dateSubscribe to HubSpot APIShare
HubSpot deprecated endpoints under the /crm/v3/* path on September 15, 2026, without setting a shutdown date. Affected numbered version paths will move to unsupported status and eventually fail. HubSpot stated that it will no longer release bug fixes, reliability improvements, or security updates for these versions.
Calls it hits
/crm/v3/*
What to use instead of these calls
Move to date-based versioning, adopting version 2026-09 such as using /crm/objects/2026-09/{objectType} in place of /crm/v3/objects/{objectType}.
In HubSpot API's words
Endpoints using numbered version paths, /v1/ , /v2/ , and /v3/ , will move to unsupported status. HubSpot will no longer release bug fixes, reliability improvements, or security updates for these versions.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Version retirement
- Announced
- September 15, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against HubSpot API's own pages
Questions
When does this change take effect?
HubSpot API deprecated /crm/v3/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: HubSpot 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 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 -
/v1/*Version retirement Stops workingin 28 days -
/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
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.