sales@webguruz.in
+1 (213) 715-5368
HubSpot has opened the 2027-03 API Beta, giving developers an early look at a new set of APIs covering automation, CMS, CRM, marketing, meetings, and revenue.
The beta introduces new capabilities for areas including workflow automation, lead scoring, AEO, contracts, payments, subscriptions, and CRM associations. It also continues HubSpot's move toward date-based API versioning, a change designed to give developers a more predictable way to work with updates to the platform.
The 2027-03 APIs are currently in beta, meaning their functionality and schemas may still change before the final release. HubSpot recommends using them for testing and development rather than relying on them as production-ready APIs at this stage.
The essential context
Biggest change: New APIs across automation, CMS, CRM, marketing, meetings, and revenue
New automation capabilities: Workflow APIs provide more programmatic control over automation
Marketing updates: New AEO, Lead Scoring, and Forms APIs expand marketing integrations
CRM updates: Auto-associations and Knowledge Base APIs add more flexibility for connected systems
Revenue APIs: New capabilities cover contracts, payments, payment settings, and subscription lifecycles
Important transition: Existing integrations need to account for HubSpot's move away from older API versions
HubSpot API update
A New API Release
Connecting tools. Unlocking new capabilities.
The 2027-03 beta represents another step in HubSpot's transition from its earlier numbered API versions toward a date-based release model.
Under the new approach, API versions are identified by dates, such as 2026-03, 2026-09, and 2027-03. HubSpot plans to introduce new date-based versions twice each year, creating clearer release points for developers working on integrations and custom applications. The company has said that supported date-based versions are designed to remain stable during their support period, helping developers plan migrations instead of dealing with unexpected changes to an existing version.
For the HubSpot developer community, the shift is significant because API versioning affects everything from custom applications to integrations that connect HubSpot with external business systems.
03 / New APIs Across HubSpot
The 2027-03 beta brings together updates across several areas of the platform.
the new Workflows API provides programmatic access for creating and managing workflows and working with custom workflow actions.
the Auto-associations API expands the ability to work with relationships between CRM records.
adds new programmatic capabilities around knowledge base articles, categories, and tags within HubSpot's CMS tools.
04 / Marketing APIs Expand Into AEO and Lead Scoring
The marketing updates in the beta also reflect some of the changes taking place across digital marketing.
One of the notable additions is the AEO API, which provides access to AI visibility data, including tracked prompts, prompt histories, and content recommendations.
The beta also introduces a Lead Scoring API for creating and managing scoring configurations and working with scoring data for CRM objects.
Alongside this, the Marketing Forms API provides programmatic management of HubSpot forms.
Together, these capabilities give developers more options for connecting marketing activity with CRM data and building customized marketing workflows.
05 / Revenue APIs Bring More Capabilities to the CRM
These additions extend the role of HubSpot beyond managing customer relationships and sales activity. Developers can now work with more parts of the revenue process directly through APIs. For businesses with complex CRM and revenue operations, that can open up new possibilities for connecting HubSpot with existing billing, payment, contract, and subscription systems.
06 / What the API Changes Mean for Existing Integrations
The new beta also comes at an important point in HubSpot's API transition.
HubSpot has announced that support for its existing v4 APIs will end on March 30, 2027. The company is encouraging developers using affected APIs to begin moving toward supported date-based versions.
This makes the new date-based model particularly relevant for businesses that have built custom HubSpot integrations over the years.
The transition does not mean every integration needs to be replaced immediately. However, businesses with custom applications will need to understand which HubSpot APIs they currently depend on and whether those APIs have a corresponding date-based version.
For development teams, this makes API planning an increasingly important part of maintaining long-term HubSpot integrations.
07 / A Broader Shift in HubSpot Development
The 2027-03 beta spans several areas of HubSpot's platform, including CRM, automation, marketing, AI visibility, payments, contracts, and subscriptions.
CRM, automation, marketing, AI visibility, payments, contracts, and subscriptions are increasingly connected within the same platform. For developers, this means more opportunities to build solutions around a company's existing HubSpot setup instead of relying only on the functionality available through the standard interface.
The new APIs give businesses more flexibility when connecting HubSpot with other tools and systems while making it easier to connect data, workflows, customer records, and revenue processes across their operations.
08 / What's Next for the 2027-03 APIs?
The 2027-03 APIs are still in beta, and some capabilities may change before the final release. For developers, however, the beta provides an early look at how HubSpot is expanding its platform across CRM, automation, marketing, AEO, and revenue.
The combination of these new APIs and HubSpot's move toward date-based versioning points to a platform becoming more open to deeper customization and integration.
