HubSpot API
/hubdb/api/v2/* version retirement
Stopped workingSubscribe to HubSpot APIShare
On December 16, 2024, the HubDB v2 API was retired. Calls to endpoints under /hubdb/api/v2/* now fail. Developers can no longer use this version to interact with HubDB.
Calls it hits
/hubdb/api/v2/*
What to use instead of these calls
Call the HubDB v3 API (/cms/v3/hubdb/*) instead.
In HubSpot API's words
HubDB v2 | December 16, 2024 | Continue working with HubDB via the HubDB v3 API instead
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Version retirement
- Takes effect
- December 16, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against HubSpot API's own pages
Questions
When does this change take effect?
Calls to /hubdb/api/v2/* on HubSpot API stopped working on December 16, 2024.
What happens to calls after December 16, 2024?
They have failed since December 16, 2024.
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 -
/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 -
No date
/contacts/v1/*Version retirement Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.