API sunsets · HubSpot · checked

HubSpot developer platform 2025.1 sunset on 1 August 2026

HubSpot developer platform 2025.1 was sunset on 1 August 2026. Since then, uploading a project on 2025.1 fails to build. The failure is loud: calls return errors. HubSpot names 2026.09 as the replacement. The date has passed, so 2025.1 can no longer be recorded as it was; compare the responses you still have with what 2026.09 returns. Find every place your code pins 2025.1: 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 developer platformCovers the platformVersion of projects (hsproject.json).
Version
2025.1
Ended
1 August 2026
After the date
calls fail
Silent?
No: calls return errors
Replacement
2026.09

What breaks after 1 Aug 2026

How to upgrade

  1. Find every place your code and config pin 2025.1: 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 2025.1 and 2026.09 in HubSpot's notes, and list the calls that touch it.
  3. 2025.1 no longer answers as it did, so compare the responses you logged before 1 August 2026 with what 2026.09 returns now.
  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 2025.1 and one at 2026.09 with the same golden, and you see which of your calls answer differently before 1 August 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 developer platform 2025.1 and replay them on 2026.09 until 1 August 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.