At Fall Spotlight on September 15, HubSpot is announcing the end of support for v1-v3 APIs, legacy public apps, and legacy private apps, all with a September 2027 enforcement date. If your integration or app uses any of these, you have a 12-month window to migrate. This changelog covers v1-v3. Support for v4 is ending on its own separate timeline, March 30, 2027, which was announced earlier this y…
This changelog rounds up the developer and builder updates in HubSpot's Fall Spotlight 2026 release: what's now generally available on Developer Platform version 2026.09, the new and updated APIs, the APIs entering public beta, and the latest AI builder tools. To learn more about what was announced during UNBOUND, visit the general Spotlight page and the developer Spotlight page. This rollup cover…
August’s developer updates expand how teams bring data into HubSpot and automate CRM operations. This month introduces webhook data sources for Data Studio, preserves active workflow enrollments when records are merged, and adds app object support to association workflow actions. Together, these changes reduce custom integration work and help automations continue with less manual intervention.
HubSpot is permanently removing the ability to create new legacy, non-Project based, private apps through the account UI. Users needing similar functionality should use Service Keys, available via Developer Platform Projects version 2026.09 or later, which supports system-to-system integrations. This sunset impacts customer accounts on two timelines based on their age. All existing legacy private…
HubSpot will sunset the Pipelines API V1 on December 4, 2026. After this date, the API will no longer be supported. If your integration relies on V1 endpoints, you'll need to migrate to the 2026-03 or newer version before the deadline to avoid disruption.
Node 18.x and 20.x are being deprecated as supported runtimes for Chatflows custom code snippets. If you have bot code snippets running on either of these versions, you need to upgrade them to Node 24.x before August 31st, 2026, or you will lose the ability to edit those snippets until the upgrade is completed.
Starting with the /2026-09/ API version shipping on September 8, 2026, HubSpot will enforce admin-configured validation rules on all CRM API write paths. If your integration creates or updates CRM records, please make sure that it conforms to the below changes before updating your version of the API.
This month's updates include a raised owner property limit, larger Webhooks Journal batch sizes, and a new historical API usage chart — plus public betas for Contract Imports and the Payment Links API. Read on for the details.
Availability: This is a breaking change for the next GA date-based API version, /2026-09/. It does not change the behavior of the current GA API version or earlier versions. Integrations will see this behavior only after moving to /2026-09/ or later. Learn more about HubSpot's Date Based Versioning What is changing? Starting in version /2026-09/ of the Pipelines API, HubSpot will validate referenc…
June’s developer updates include new CRM and customer success signals, cleaner subscription-status histories, expanded Knowledge Vault support for structured data, app object activity association controls, quote module customization, and several CLI improvements. This roundup also covers custom event timeline configuration and new Remote MCP server capabilities for content analytics and landing pa…
The HubSpot Agent CLI is a new command-line interface purpose-built for AI agents to interact with your HubSpot CRM data — reading records, running searches, creating and updating objects, managing pipelines, properties, associations, workflows, and more. It's designed for agentic environments like Claude Cowork, Claude Code, and OpenAI Codex, and is particularly well-suited for scheduled automati…
We’ve improved our SDK releases to support date-based API versioning, the new /YYYY-MM/ format introduced across HubSpot’s APIs. Generated from a centrally managed API specification, SDKs now cover more endpoints across multiple languages and release faster, so your clients stay aligned with the APIs you're building on.
This month brings a set of updates aimed at making everyday building better. Breeze Assistant steps further into your workflows, a new useCrmSearch hook shipped for UI extensions, stage calculated properties available for custom objects and the HubSpot CLI got a fresh round of improvements — plus updates to blog author attribution, IP range webhooks, and more. Read on below for the details.
On March 30, 2027, HubSpot v4 APIs will move to an unsupported state. After that date, v4 APIs will no longer receive updates, bug fixes, or stability guarantees from HubSpot.
We have introduced the latest date-based, versioned OAuth API for token issuance and introspection, as announced previously here. As adoption of the new OAuth API grows, we are beginning to deprecate the legacy v1 OAuth API. As part of this transition, a new REVOKE endpoint is also being introduced for the latest date-based versioned OAuth API, and the v1 API will be fully deprecated on February 1…
We're updating the requirements for listed and certified apps in the HubSpot Marketplace to align with current platform standards and deprecations. These updates ensure that apps stay compatible with HubSpot's evolving platform and APIs, providing customers with a more reliable, secure experience.
What’s changing? We’ve recently shared our vision for building an open ecosystem for the agent era here. To reflect how developers, customers, and agents are actually building on HubSpot today, we’ve also updated our Developer Terms and Technology Partner Program Agreement. Including:
This month, on top of all the of the amazing updates and releases from Spring Spotlight 2026, we also have updates regarding the availability of our legacy CRM card migration tool, new features for the Custom Channels API, and more. Make sure to read on below for more details.
Beginning May 26, 2026, the ability to create new legacy public apps via the Developer Platform UI will be permanently disabled. New public app development should use the Projects-based app platform.