Pipelines API v1 retired on 2026-12-04
- Provider
- HubSpot
- Endpoint
* /crm-pipelines/v1/**- Effective
- 2026-12-04
- Severity
- high
- Change
- version-sunset
- Status
- verified
- Automatic fix
apply-fix
What changed
HubSpot retires the legacy CRM Pipelines API v1 on 2026-12-04; after that, calls to v1 endpoints stop working. The replacement is the Pipelines API 2026-09 version (GA 2026-09-09). The /crm-pipelines/v1 path comes from HubSpot's legacy v1 reference; the notice itself names no paths.
What to do
Call GET /crm/pipelines/2026-09/{objectType} (HubSpot's OpenAPI spec for the 2026-09 Pipelines API) instead of /crm-pipelines/v1/pipelines/{objectType} before 2026-12-04. The response keeps results[] and stages[], but pipelines and stages are identified by id instead of pipelineId and stageId.
Sources
- Provider notice (2026-08-14)
- https://developers.hubspot.com/docs/api-reference/latest/crm/pipelines/guide
- https://github.com/HubSpot/HubSpot-public-api-spec-collection/blob/main/PublicApiSpecs/CRM/Pipelines/Rollouts/145896/2026-09/pipelines.json
Check your code
bash
npx shapi-cli scan .shapi scan lists the call sites this change affects; shapi fix repairs them test-first when the advisory has an automatic fix. All advisories · Markdown · OSV · JSON