HubSpot Developer Changelog

HubSpot will migrate content rendering from the legacy Java Runtime Environment (JRE) locale dataset to the Common Locale Data Repository (CLDR), the current industry standard for localization. Most content will remain unchanged, while some ...

Today we're introducing a new versioning system for our APIs, using a /YYYY-MM/ format (like /2026-03/) instead of v1, v2, v3, v4 to denote the month in which the API was shipped. This date-based versioning gives ...

This month's rollup introduces exciting updates designed to streamline developer workflows and enhance visibility. Key highlights include the ability to view app objects directly within the Data Model Builder and a faster, video-based review ...

We’ve added a confirmation dialog when HubSpot users install third-party apps that haven’t been reviewed by ...

In February, HubSpot introduced a set of updates focused on improving developer visibility, extensibility, and platform flexibility. From enhanced OAuth install logging and Custom Events for Pro customers to deeper CRM associations and UI ...

The HubSpot connector for ChatGPT can now create and update CRM records and log activities directly from ChatGPT’s chat window, including new contact and deal creation, and logging notes or tasks.

The local HubSpot Developer MCP Server is now generally available, enabling developers to create apps and CMS assets through agentic tools like VS Code, Claude Code, Cursor, OpenAI Codex, Gemini CLI, and other MCP-compatible ...

Starting May 11, 2026, HubSpot will resume the automatic migration of accounts from the legacy Cookie Consent Banner (v1) to the current version (v2). This process was

All legacy developer accounts are being upgraded to HubSpot’s new unified Developer Platform experience. This migration brings developer tools and resources together into a single HubSpot account, replacing older, separate tools with one ...

January’s developer updates ...