HubSpot’s Pipelines API v1 stops responding after 4 December 2026
Legacy Bridge knows 9 v1 pipeline calls: 3 translated in full, 4 with documented limits, 2 not translated. It performs the 7 it translates on the date-based Pipelines API, so a call sent to the bridge still gets an answer after that date, within the limits listed below. The 2 it does not translate — create and delete a pipeline on the older Deals API — get HTTP 501.
What HubSpot announced
- HubSpot announced on 14 August 2026 that it sunsets the Pipelines API v1 on 4 December 2026; v1 endpoints stop responding after that date.
- HubSpot’s legacy reference for the Pipelines API v1 (pages get, create, update and delete, last modified 27 July 2026) shows a banner with another date: 2 November 2026. The two HubSpot pages disagree; this page goes by the changelog, the later one (14 August 2026).
- It asks integrations to move to the 2026-03 or a newer version of the Pipelines API before the deadline, and recommends 2026-09.
- The notice names the API, not its paths.
- The v1 to v3 APIs as a whole are a separate announcement (15 September 2026): they become unsupported after September 2027, with no more bug fixes, reliability improvements or security updates, and HubSpot has not announced a shutdown date for them.
Sources: HubSpot developer changelog, Pipelines API V1 Sunset: December 4, 2026 and Legacy APIs and Apps: What’s Going Unsupported and When; checked on 2 October 2026.
The calls Legacy Bridge knows
This list is generated from the bridge’s registry, so it cannot claim more than the code does. Each call is performed on the date-based Pipelines API (the arrow); a partly translated one says what that API does not carry.
Pipelines v1 — /crm-pipelines/v1/pipelines
The 4 calls of HubSpot’s legacy reference for Pipelines v1.
| Call | Bridge |
|---|---|
GET /crm-pipelines/v1/pipelines/{object_type}→ GET /crm/pipelines/2026-09/{objectType} — the pipeline `default` flag and includeInactive are not available in the date-based API | Partly translated |
POST /crm-pipelines/v1/pipelines/{object_type}→ POST /crm/pipelines/2026-09/{objectType} — pipeline and stage ids are assigned by HubSpot; the `default` flag is inferred | Partly translated |
DELETE /crm-pipelines/v1/pipelines/{object_type}/{pipeline_id}→ DELETE /crm/pipelines/2026-09/{objectType}/{pipelineId} | Translated |
PUT /crm-pipelines/v1/pipelines/{object_type}/{pipeline_id}→ PATCH /crm/pipelines/2026-09/{objectType}/{pipelineId} — applied stage by stage (PATCH, stage PATCH/POST/DELETE); new stage ids are assigned by HubSpot; the `default` flag is inferred | Partly translated |
Deal pipelines v1 — /deals/v1/pipelines
The older Deals API had five pipeline calls: list, get, create, update and delete (HubSpot’s archived pages; its reference no longer documents them). The notice does not say whether they are part of this sunset; they are v1 pipeline calls, so plan for the same date. Legacy Bridge translates 3 of the five:
| Call | Bridge |
|---|---|
GET /deals/v1/pipelines→ GET /crm/pipelines/2026-09/deals | Translated |
POST /deals/v1/pipelineslegacy v1 endpoint retired from the HubSpot reference; not translated yet | Not translated |
DELETE /deals/v1/pipelines/{pipelineId}legacy v1 endpoint retired from the HubSpot reference; not translated yet | Not translated |
GET /deals/v1/pipelines/{pipelineId}→ GET /crm/pipelines/2026-09/deals/{pipelineId} | Translated |
PUT /deals/v1/pipelines/{pipelineId}→ PATCH /crm/pipelines/2026-09/deals/{pipelineId} — applied stage by stage (PATCH, stage PATCH/POST/DELETE); new stage ids are assigned by HubSpot | Partly translated |
The two marked “Not translated”, POST /deals/v1/pipelines (create) and DELETE /deals/v1/pipelines/{pipelineId} (delete), Legacy Bridge answers with HTTP 501 and the error category BRIDGE_UNSUPPORTED. Make those two calls on the date-based Pipelines API in your own code.
Two ways to be ready
- Rewrite the calls on the date-based Pipelines API, as HubSpot asks.
- Keep the code, change the base URL. Send the call to Legacy Bridge instead of HubSpot and it answers in the v1 shape. See the connection guide.
Find these calls in your code
The free scanner lists every legacy HubSpot call in a ZIP of your integration or a list of URLs, shows which of them the bridge translates, and groups them by the date HubSpot gives; the Pipelines API v1 comes first. Nothing from your code is stored.