HubSpot introduces date-based API versioning with twice-yearly releases
HubSpot introduced date-based API versioning on March 30, 2026, replacing v1 to v4 labels with a YYYY-MM format. Breaking changes ship only in March and September, and each version gets at least 18 months of support.
By Cora Whitley, GTM AI Analyst, Chief of StaffHubSpot's March 30, 2026 changelog post introduced date-based API versioning across most of its recent APIs, after first announcing it for CRM APIs at Fall Spotlight 2025. Versions are named for the month they ship, released each March and September, and supported for at least 18 months. HubSpot says the change is meant to make breaking changes predictable, reduce unexpected integration failures and make the APIs easier for AI agents to use. Developers already on the latest v3 or v4 API can move by updating the URL path.
The details
- Version format: /YYYY-MM/, for example /2026-03/.
- Release schedule: March (Spring Spotlight) and September (INBOUND).
- Minimum support window: 18 months per version, up from a 90-day minimum deprecation notice.
- Beta APIs released after /2026-03/ use /2026-09-beta/.
- The /2025-09/ CRM APIs become unsupported with /2027-03/; v4 APIs are supported until March 2027.
- On May 21, 2026, HubSpot confirmed v4 APIs move to unsupported status in March 2027.
Context
GTM Tech News covered HubSpot's Spring 2026 Spotlight on April 14, 2026, which launched HubSpot AEO and Smart Deal Progression. The versioning change was published two weeks earlier for developers. In September 2026 HubSpot set a September 2027 end of support for v1 to v3 APIs and legacy apps, building on this versioning scheme.
Not disclosed
- Which APIs are not yet on date-based versions
- Whether unsupported versions will be switched off on a fixed date
- How Marketplace partners are notified of breaking changes
- Vendor
HubSpot- Category
- CRM & Marketing Automation
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
