HubSpot API versioning has been a source of quiet pain for developers building on the platform for years. The v1, v2, v3, v4 naming system was inconsistent across APIs, deprecation windows were short, and breaking changes arrived without a predictable rhythm. As of March 2026, that changes.
For context: an API, or application programming interface, is essentially the connection layer that allows external software to talk to HubSpot, pulling contact data, pushing updates, and triggering workflows. Versioning is how HubSpot signals to developers that the API has changed.
Under the old system, those signals were inconsistent. Different parts of the API used different version numbers, deprecation notices were short, and breaking changes–updates that would cause an existing integration to stop working–could arrive with as little as 90 days’ warning.
For teams maintaining multiple integrations, this created ongoing maintenance overhead with no predictable rhythm.
That being said, HubSpot has moved to date-based versioning for its public APIs, replacing the numeric scheme with a /YYYY-MM/ format. The first release under the new system is /2026-03/, and the company has confirmed the pattern will follow a fixed cadence: new versions ship every March and September.
Each version is immutable once released, meaning breaking changes only arrive in a new version, never mid-lifecycle. The minimum support window per version is 18 months. The change was announced as part of HubSpot’s Spring 2026 Spotlight developer changelog, published in late March.
What changes for developers
For anyone currently building on HubSpot APIs, the practical implications are straightforward. The /2026-03/ release covers the most recent API surfaces and is based on the latest v3 and v4 endpoints. If you are already on the most current version of a given API, migrating means updating the URL path, swapping /crm/v3/ for /crm/objects/2026-03/, for example.
Older versions stay supported on the following timeline. The /2025-09/ CRM APIs announced at INBOUND 2025 remain supported until the /2027-03/ release. Current v4 APIs are supported until March 2027. Legacy v1 through v3 APIs continue to function, with their support timeline to be announced separately, though HubSpot has already signalled that v1 deprecations are moving forward, with the Contact Lists API v1 sunsetting on April 30, 2026.
HubSpot’s developer documentation states the rationale plainly: “Historically, it was hard to answer basic questions about which version to use, when things would change, and how to plan updates. Date-based versioning is designed to fix that.”
Why the cadence matters
The twice-yearly release schedule–March and September, aligned with HubSpot’s broader platform release cadence–gives development teams something they have not had before with HubSpot integrations: a predictable planning horizon.
Previously, developers had to monitor changelog updates continuously and absorb breaking changes with 90-day minimum deprecation notices. The 18-month support window per version is a significant expansion of that runway. Teams maintaining multiple integrations can now align upgrades with their own release cycles rather than reacting to HubSpot’s internal schedules.
The developer platform is moving to the same date-based naming convention in parallel. Platform Projects version 2026.03 became generally available on March 30, 2026, aligning with the API version naming without introducing functional dependencies between the two tracks.
The MCP server is now generally available
Buried in the same Spring Spotlight release is a separate update worth noting. HubSpot’s remote MCP server–which allows MCP-compatible clients to connect to HubSpot data and workflows–has graduated from beta and is now generally available to all HubSpot accounts.
The GA release adds write capabilities, engagement history, marketing content objects, and organisational context. For developers building AI agents or agentic workflows on top of HubSpot, this matters: MCP compatibility means agents can now interact with HubSpot CRM data using the same protocol standard that has become the default mechanism for agent-to-tool connectivity across the broader AI ecosystem.
HubSpot noted in the changelog that AI agents and MCP-based integrations can now rely on a consistent, machine-friendly versioning model, which is the practical benefit of date-based versioning beyond human developers. An agent navigating versioned endpoints needs the same predictability that any developer does.
Source: HubSpot Developer Changelog, Spring 2026 Spotlight; HubSpot Developer Documentation, date-based API versioning guide; HubSpot 2026-03 API Reference.
See also: AI discovers bugs faster than teams can respond
Want to learn more about cybersecurity from industry leaders? Check out Cyber Security & Cloud Expo taking place in Amsterdam, California, and London. The comprehensive event is part of TechEx and is co-located with other leading technology events including the AI & Big Data Expo. Click here for more information.
Developer is powered by TechForge Media. Explore other upcoming enterprise technology events and webinars here.