# The CMS performance API stops working

Calls to GET /cms/v3/performance* on HubSpot API stopped working on April 9, 2024.

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.

## What to use instead

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.

- API: HubSpot API (api.hubapi.com)
- Kind: Removal
- Takes effect: April 9, 2024
- Calls after that day: fail
- Calls it hits: `GET /cms/v3/performance*`
- Source: [Announcement](https://developers.hubspot.com/docs/api-reference/deprecated-apis)
- Verified: November 6, 2026, against HubSpot API's own pages
- Page: https://www.okapi.bot/providers/hubspot-api/breaking-changes/the-cms-performance-api-stops-working/

## HubSpot API's words

> CMS performance | April 9, 2024 | For website analytics data, use the analytics API.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent