HubSpot API
CMS performance API removal
Stopped workingSubscribe to HubSpot APIShare
On April 9, 2024, the CMS performance endpoints were shut down. Requests to GET /cms/v3/performance* now fail rather than returning performance metrics. Applications relying on these calls must be updated to retrieve their data through alternative endpoints.
Calls it hits
GET /cms/v3/performance*
What to use instead of these calls
Use the analytics API (/analytics/v2/reports/*) to read website analytics instead. The move requires more than changing an identifier, as the analytics API reports different figures than CMS performance, and your team must evaluate whether they serve the same purpose.
The analytics API reports other figures than CMS performance; whether they serve the same purpose is the team's call.
In HubSpot API's words
CMS performance | April 9, 2024 | For website analytics data, use the analytics API.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Removal
- Takes effect
- April 9, 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 GET /cms/v3/performance* on HubSpot API stopped working on April 9, 2024.
What happens to calls after April 9, 2024?
They have failed since April 9, 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 -
/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.