API sunsets · HubSpot · checked

HubSpot Pipelines API v1 sunset on 4 December 2026

HubSpot Pipelines API v1 is sunset on 4 December 2026. After it, every call to a Pipelines v1 endpoint stops working. The failure is loud: calls return errors. HubSpot names 2026-09 as the replacement (HubSpot recommends 2026-09, generally available from 9 September 2026; 2026-03 or newer also works). Record your real calls on v1 before the date and replay them on 2026-09: after it, nobody can record what v1 returned. Find every place your code pins v1: npx --allow-git=root github:agentwares/api-sunset scan

$ npx --allow-git=root github:agentwares/api-sunset scan

npx --allow-git=root github:agentwares/api-sunset scan lists every API version your code and config pin (Shopify, Meta Graph, Google Ads, HubSpot, Stripe and the rest of this list) with its end date, what breaks and this page's link. It needs no account and no API key, reads your files on your machine and sends nothing; its one request fetches this data. Free and MIT licensed.

The facts

API
HubSpot Pipelines APICovers /crm-pipelines/v1/ endpoints.
Version
v1
Announced
14 August 2026
Ends
4 December 2026
After the date
calls fail
Silent?
No: calls return errors
Replacement
2026-09HubSpot recommends 2026-09, generally available from 9 September 2026; 2026-03 or newer also works

What breaks after 4 Dec 2026

How to upgrade

  1. Find every place your code and config pin v1: npx --allow-git=root github:agentwares/api-sunset scan prints each file and line, and the variable name for a .env file, never its value.
  2. Read what changed between v1 and 2026-09 in HubSpot's notes, and list the calls that touch it.
  3. Before 4 December 2026, send your real calls to v1 and to 2026-09 and compare the answers: same status, same fields, same values where they should match; after it, nobody can record what v1 returned.
  4. Change the version string, deploy, and watch the first day's responses.

Record your real calls on the old version before the date, and replay them on the new one.

agentcheck runs scheduled checks of an endpoint. A check sends the request you define (a path or a full URL, a method and a body, with your API key as a header, stored encrypted) on a schedule and compares each response with a golden: exact text, contains, a regular expression or a JSON Schema, none of which costs an LLM call. When a response stops matching, it opens an incident and alerts you. Point one check at v1 and one at 2026-09 with the same golden, and you see which of your calls answer differently before 4 December 2026.

Free: 1 monitored target, hourly checks, badge and public status page. Starter: 3 targets, 5-minute checks, Slack and Discord alerts, 30-day history. Recording the calls your code already makes is a different path: the trace import (POST /api/v1/targets/{id}/traces, or the agentcheck_record MCP tool) takes agent traces, a prompt and an answer, and turns them into checks judged by the LLM judge (Pro). It does not take raw HTTP requests and responses, so for an API the scheduled checks are the way in today.

Migration watch is not built. It would record the calls your code makes to HubSpot Pipelines API v1 and replay them on 2026-09 until 4 December 2026, with nothing to set up, and email you what answers differently. If you would pay for that, say so with one click. The click is counted; nothing else is sent or stored.

Other HubSpot dates

Every API sunset, by date

Sources

Built only from HubSpot's own pages. No intent is implied: a date is what the page says on the day it was read. Data: /apis/sunsets.json.

api-sunset is a free tool from agentcheck, which runs scheduled checks of your endpoints and alerts you when an answer changes.