HubSpot API
Ecommerce Bridge API removal
Stopped workingSubscribe to HubSpot APIShare
On February 28, 2023, the Ecommerce Bridge API stopped working. Calls targeting the /extensions/ecomm/v2/* endpoints now fail.
Calls it hits
/extensions/ecomm/v2/*
What to use instead of these calls
Integrations should switch to using HubSpot's CRM v3 APIs. Write products, deals and line items with the CRM v3 object APIs (/crm/v3/objects/*), with calls authenticated by an app.
In HubSpot API's words
Ecommerce bridge | February 28, 2023 | Integrations should switch to using HubSpot’s CRM v3 APIs, with calls authenticated by an app.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Removal
- Takes effect
- February 28, 2023
- 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 /extensions/ecomm/v2/* on HubSpot API stopped working on February 28, 2023.
What happens to calls after February 28, 2023?
They have failed since February 28, 2023.
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 -
/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 -
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.