Hubspot Developers Release Notes

February updates from HubSpot

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 extension improvements, this month’s releases are designed to make building, managing, and scaling apps on HubSpot easier and more powerful.

Here are some important updates from February that affect external developers...

Code Sharing for UI Extensions

You can now share code between UI extensions. Previously, if your App Cards, App Homes, and Settings pages required the same code types, utilities, and components, you had to copy the code for each instance. This meant that whenever you made updates, you had to revise every copy of that code separately.

In the unified developer platform, your app cards, app homes, and setting pages are all part of the same app. With npm workspace support, your UI extensions can share the same codebase. Define your types once, write your API client once, and build a component library your whole project uses.

Associate Payments with Tickets

Payments can now be directly associated with tickets. In the UI, you can add a CRM card for Payments to the Tickets record page. Then, you can use this CRM card to directly connect the ticket you’re on to a Payment.

If you’re using the Tickets API endpoint for associations, you can use the HubSpot-defined associationTypeId of 1355. To associate a payment with a ticket, use the associationTypeId of 1354.

OAuth Install Event Logs

We’re adding OAuth install event logs to the Developer Platform, providing enhanced install visibility for all apps built on version 2025.2 or newer.

What’s new or changing?

• OAuth Install Event Logs: Developers can now track all OAuth app installation attempts, including whether an install succeeded and where failures occurred.

• Visibility into Install Flow: Logs will record key stages:

  • Install start (consent shown).
  • Install callback (user clicks Connect).
  • Token exchange (install completes).

• Filtering and Exporting: Logs can be filtered in the Developer Platform and exported via integrated observability tools or downloaded as CSV files.

This functionality is available for apps built on the Developer Platform v2025.2+. Please migrate your app if you wish to leverage install event logs. To access logs, go to Development > Monitoring > Logs in your HubSpot account. Set up observability integrations if you’d like logs exported automatically.

This change helps developers quickly identify and resolve installation issues and will improve the overall app install experience for customers using the Developer Platform.

Tech Partner Program Tiering

Technology Partner tiers help customers identify app developers who consistently deliver high-quality experiences in the HubSpot ecosystem. Tiers: Partner, Rising, Leading, and Premier are assigned at the developer level (not per app) and appear on Marketplace listings and filters.

Tier upgrades are evaluated quarterly based on performance over the previous 12 months, with downgrades beginning semiannually in 2027. Developers can track their current tier, progress toward the next level, customer value metrics, and influenced revenue in the Technology Partner dashboard, which updates monthly and is available to partners with an approved Marketplace listing using HubSpot developer tools.

To access the required Partner POC form (for Leading and Premier tiers), click Partner POC Form in the upper right of your dashboard.

To report closed deals or new accounts you influenced, click Submit influenced revenue and complete the form. See the Technology Partner Program Guide for details.

Connected Apps: New Connections Home & Connection Insights

Connections Home is a new centralized page for managing your integrations. It provides a comprehensive view of apps connected to your account, apps requiring immediate attention, and apps installed by other users across your organization.

This update also includes a new Connection Insights section that provides a detailed overview of app activities, Academy content, new API call usage, and new Record Insights that track how your apps interact with HubSpot and CRM data.

To view the new Connections Home, navigate to Settings > Integrations > Connected Apps. It includes three key sections:

• Needs Your Attention highlights app statuses and notifications, such as expired or disconnected connections, so you know what to fix first.
• My Apps displays all apps connected to your account, including connection status, install details, and recent activity.
• Other apps installed by users in my organization show all apps connected by users across the organization.

From the new Connection Insights page, you will find:

• App log & activities: View recent app activity, including connections, disconnections, and other key events, with filters for users and apps.

• Academy: Access relevant learning content to better understand and manage your connected apps.

• API call usage [new]: Track your daily API call usage across all private apps to monitor activity before reaching your limit, preventing disruptions caused by hitting API maximums. Note: API usage insights are also available within each individual app’s settings page.

• Record Insights [new]: This is a new section under Connection Insights that shows how apps are interacting with your CRM data. This includes daily record event counts broken down by app, which record types were affected, and the type of action taken (Created, Updated, Deleted, Merged). Note: Record insights are also available within each individual app’s settings page.

Custom Events Are Now Available to the Pro Platform

Custom events are now available to all Pro customers. Previously an Enterprise-only feature, Custom events let you track any behavioral data that matters to your business, such as product usage, purchasing behavior, offline interactions, third-party platform activity, and changes to properties inside HubSpot.

Note: Pro customers are limited to 10 million event occurrences per month. Enterprise customers are limited to 30 million event occurrences per month. Both Pro and Enterprise customers can define up to 500 distinct event types.

See the Knowledge Base article and product update for more details, and our Developer Documentation for instructions for using custom events.

Public Beta: Conversation & Workflows Ownership Updates

We’re introducing additional functionality to conversation-based workflows in Service Hub Professional and Enterprise subscription tiers in HubSpot Workflows & Inbox. These betas enhance ownership flexibility by adding a new “No Owner” option to the Assign Conversation Owner action and extending the Rotate record-to-owner action to work with conversations.

Together, these updates give support teams more structured, automated control over conversation routing and handoffs, while respecting inbox permissions.

What’s new or changing?

• New “No Owner” option (Assign Conversation Owner action)

  You can now automatically remove a conversation's owner via workflow. Previously, unassigning a conversation required manual updates or workarounds. With this update, workflows can clear ownership and return conversations to an unassigned state based on your defined criteria.

  How it works:

  • The Assign Conversation Owner action now displays a “No Owner” option at the top of the user list.
  • Selecting “No Owner” removes the current owner and returns the conversation to the inbox’s unassigned state.
  • This can be added to any conversation-based workflow.

• Rotate record to Owner is now available in conversation-based Workflows

  The existing Rotate Owner action has been extended to conversations. This action automatically moves a conversation to another inbox and assigns it to the appropriate user or team based on inbox access, bringing structured, automated handoffs (similar to CRM object rotation) to Service Hub conversations.

  How it works:

  Within conversation-based workflows:

  • Add rotate record to the owner from the CRM action list.
  • Select a target inbox (active, non–Help Desk inboxes only).
  • Choose your assignment method:
    • Customer Agent
    • Specific users or teams (with inbox access)
    • Contact owner (with fallback options)
    • No owner (to leave the conversation unassigned)
  • Configure availability settings (e.g., assign only to available users).
  • Save the action.

  Conversations enrolled in the workflow will be moved to the selected inbox and assigned based on your configuration.

  Note: Changing the assignment on closed conversations will reopen them. We recommend excluding closed conversations from enrollment criteria. If using rules-based bots, exclude bot-based chatflows from enrollment and use the Send to Team Member action inside the chatflow for routing instead.

  To get started, in your HubSpot account, click on Product Updates > search “Assign Conversation Owner Update — New “No Owner” and “Rotate Record to Owner action in Conversation-based Workflows”, and click “Join Beta” for each.

  Please refer to the linked documentation for additional information.

• Auto-Enrollment for Developer Platform Betas

  HubSpot is introducing a one-time “Join beta” opt-in that grants developers ongoing access to all current and future Developer Platform betas—no need to request access each time a new beta version ships. After enrolling and accepting the Beta Terms, you can build and deploy against a beta by referencing it in hsproject.json (for example, "version": "2026.03-beta"), and you’ll automatically stay enabled for future betas as they’re released. Learn more in the Product Update entry and review how platform versioning works in the docs: Product Updates and Platform Versioning.

Questions or comments? Join us in the Developer Community Forum for a peer-to-peer discussion.

Original source Report a problem

What’s New

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.

Additionally, You can also now access products, line items, invoices, orders, carts, segments (lists), and engagement history from calls, emails, meetings, tasks, and notes.

Watch Demo: Update your CRM with ChatGPT

Please note:

• If your HubSpot account has sensitive data enabled, the HubSpot connector for ChatGPT will not have access to any engagement data for added security.
• When using create and update actions in the HubSpot connector for ChatGPT, attribution will be recorded in your HubSpot account’s Audit Log to the user and the ChatGPT connector.
• The HubSpot connector for ChatGPT supports bulk Create and Update actions for a maximum of 10 records in a single request.

Why Does It Matter?

With expanded write access and engagement visibility, the HubSpot connector for ChatGPT allows you to update your HubSpot context directly without leaving ChatGPT. Ask ChatGPT to log a discovery call, create follow-up tasks, update deal stages, or analyze months of customer emails using natural language.

By accessing engagement history such as emails, tasks, and notes, ChatGPT can surface meaningful insights and let you take action on them instantly, right from the chat window. This unlocks faster, more intelligent use cases, like:

• Faster workflows: Create a task to follow up with a prospect who has questions on pricing.
• Smarter insights: ChatGPT can now access your email threads and call notes to provide context-aware recommendations.
• Less manual work: No more copying insights from ChatGPT into HubSpot properties manually – update directly from ChatGPT’s chat window.
• Better decisions: Analyze real customer conversations, not just CRM snapshots.

How Does It Work?

To access these new capabilities, you'll need to upgrade to the latest version of the HubSpot connector in ChatGPT. If you're setting up the HubSpot connector for the first time, review the setup steps here.

Watch: How to set up HubSpot app inside ChatGPT

Approve the updated app (ChatGPT admin required)

If you're a ChatGPT workspace admin, you'll see an "Enable the updated HubSpot app" pop-up when you open ChatGPT. Click "Enable for workspace" to approve it for all users.

You can also navigate to the HubSpot app from the ChatGPT App Directory and open it in Admin Console to enable it for your workspace.

Update the app (non-admin users)

After admin approval, individual users can upgrade the app:

1. In your ChatGPT chat window, click your profile icon in the bottom left.
2. Click Settings, then Apps, and select HubSpot.
3. In the upper right, click Upgrade.
4. Follow the prompts to re-authenticate the app.
5. When re-authenticating, make sure to select all necessary permissions to access write actions, newly added objects, and engagement history.

Using the HubSpot connector

1. In your ChatGPT window, click the + icon, then More.
2. Click HubSpot to enable the app. If your prompt includes the word "HubSpot," the app will turn on automatically.
3. Add your prompt and press Enter.

Example Prompts

Example Prompts

Updating CRM context (write access):
The HubSpot connector for ChatGPT can update your CRM directly.

• “Create a new contact for [X] at with their email [insert email address]”
• “Update the deal ‘Enterprise Package Q4’ to Closed Won.”
• “Log a note on this ticket summarizing our resolution approach.”
• “Create a task for me to follow up with [X] next Tuesday about contract renewal.”

Engagement visibility:
The HubSpot connector for ChatGPT can now access your communication history to provide richer context.

• Sales: “Summarize all my emails with [X] from the last month and list any issues that might affect deal closure.”
• Marketing: “Create Follow-Up Tasks from Recent Email Opens”
• Service: “Show me all open tasks assigned to me this week, sorted by priority.”

For more prompts, please visit our prompt library.

Additional Best Practices

• Start small by updating a single record before making bulk changes.
• Always review the proposed changes that ChatGPT shows before execution and take a moment to confirm them.
• For the best results, use the latest models.

Please note: A Super Admin or a user with App Marketplace permissions in your HubSpot account must connect the connector for the first time or, if already installed, uninstall and re-connect and select the allowed / updated permissions for it. Once this is done, they can give access to other users to connect it.
Learn more about how you can manage access to the connector.

The HubSpot connector for ChatGPT respects user permissions, users will only see the CRM context they’re allowed to access in HubSpot. For example, individual sales reps will only see pipeline data for deals they have permission to view or update.

The HubSpot connector for ChatGPT responds in the language used by the user, if supported. For the full list of supported languages, please refer to OpenAI’s multilingual documentation & supported countries and regions.

Who Gets It?

The HubSpot connector for ChatGPT is available to all HubSpot customers across all tiers with an OpenAI account.

Questions or comments?
Join us in the Developer forums.

Original source Report a problem

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 tools.

This local server connects agentic tools directly to HubSpot's developer platform, and empowers them with the context of HubSpot's developer documentation allowing developers to accomplish complex development tasks using natural language instead of having to manually parse docs, run CLI commands, or implement APIs.

Previously available as a beta, the general availability of the HubSpot Developer MCP Server brings full production support and stability to a workflow that's been proven across real development scenarios.

With this update, developers can:

• Build and iterate on apps — Scaffold, configure, and iterate on HubSpot apps without context-switching between tools.
• Create and manage CMS themes, templates and modules — Create and manage CMS assets like templates and modules directly from their AI tool.
• Manage serverless functions — Create, update, and troubleshoot HubSpot serverless functions through natural language prompts.
• Access app analytics — Query app performance and usage data conversationally to understand how integrations are performing.
• Troubleshoot with context — Debug and resolve issues faster with an AI assistant that has direct access to your HubSpot developer environment.

The HubSpot Developer MCP Server handles the repetitive, context-heavy parts of the development so you can spend more time building. For implementation details, see the developer documentation here.

When is it happening?

The Developer MCP Server is now generally available as of February 19, 2026, open to all developers building on the HubSpot platform.

Questions and comments?

Join us in the Developer forums.

Original source Report a problem

Starting May 11, 2026

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 previously announced and later paused to allow more time for manual adoption. This update ensures all accounts use a banner that meets modern accessibility standards and supports the latest privacy features. While the migration happens automatically on this date, you can manually opt-in ahead of time to test the new version within your account.

What's changing?

The v2 Cookie Consent Banner features an updated design, groups banners by domain, and includes features like support for Global Privacy Control (GPC), opt-out banner types, and expanded customization options.

This migration changes the HTML structure of the cookie banner. If you use custom CSS or JavaScript to modify your banner's appearance or behavior, you may need to update your code to remain compatible with the v2 structure.

Key considerations for developers:

• Updated HTML: You may want to review any CSS and JavaScript that previously targeted the cookie banner HTML because the HTML is changing.
• Refined styling: The v2 banner supports more customization options within the HubSpot UI, which may eliminate the need for some of your existing custom CSS. We encourage you to rely on the built-in customization options over custom CSS whenever possible to simplify future upgrades if privacy regulations change.
• Manual Testing: You can opt into the v2 migration manually in your banner settings to verify that your site's styling and scripts continue to function as expected before the automatic update.

When is it happening?

This change goes into effect on May 11, 2026.

Questions or comments?

Join us in the developer forums.

Original source Report a problem

January’s developer updates focus on making HubSpot apps more flexible, scalable, and integration-friendly. Highlights include major improvements to UI Extensions, expanded API capabilities, enhanced sandbox and event management, Marketplace analytics upgrades, and new public betas that unlock deeper access to forecast and subscription data.

• UI Extensions: p_* wildcard enables cards for all custom objects
• Breeze Studio agents upgraded to GPT-5
• Sync Single Sign On (SSO) Settings to Sandbox and Developer Accounts
• Enhanced Quote Design with HTML Editing
• Custom events can now be deleted
• New Sandbox Listing Page
• Pre-rendering warnings now appear in Design Manager
• Breeze Customer Agent Now Supports Omnichannel Deployment via Custom Channels API
• New Campaign Asset Type Associations via Campaigns Public API
• Company Lifecycle Stage Properties
• Partner Search Analytics
• Marketplace Updates
• Custom event updates
• Public Beta: Forecast Read API
• Public Beta: Securely generate a preference page URL

UI Extensions
UI Extensions now supports a p_* wildcard in card configuration, letting you target all custom object types in a portal without listing individual schema names (like p_my_object) or portal-specific fully qualified names (like p123456_my_object). This removes a major blocker for public apps, since custom object names vary by customer portal—apps can now work across any customer’s custom objects without hardcoding object IDs. To use it, set the object target in your card config to p_* instead of a specific custom object name.

Breeze Studio agents upgraded to GPT-5
Breeze Studio agents now default to GPT-5 instead of GPT-4.1, including Marketplace agents like Deal Loss, Customer Health, Customer Handoff, and Social Post, as well as custom agents in private beta. Developers and customers should see improved reasoning and overall agent performance, with no action required for new agents. Existing agents created before December 1 have been automatically upgraded as of January 12, 2026—note that this change does not affect the Customer, Prospecting, or Data Agents.

Sync Single Sign On (SSO) Settings to Sandbox and Developer Accounts
When you enable Single Sign-On (SSO) on a production account, those settings now automatically carry over to any newly created Sandbox or Developer test accounts. This simplifies security setup and ensures non-production environments meet the same authentication standards without extra configuration.
Note that this does not retroactively apply to existing sandboxes created before SSO was enabled on production.

Enhanced Quote Design with HTML Editing
Commerce Hub quotes now support source code editing in the rich text editor, allowing users to view, edit, or directly write the underlying HTML. This unlocks advanced customization for quote templates, including custom layouts, branding styles, responsive content, and embedded assets that go beyond standard rich text controls. Template creators can now build quotes that behave more like modern web pages, eliminating fragile workarounds like image-based layouts.
How does it work?

• Going to Settings > Objects > Quotes > Quote Templates
• Within the Quote Template Editor, click into any content section
• Click Advanced > Source Code
• Edit the HTML and click “Save changes”
• Review the rendered content before publishing the quote template
  Quotes created from the quote template will automatically pull in the source code into the rich text sections. Source code cannot be edited at the quote-level.
  Learn more in the Commerce Hub Quotes documentation.

Custom events can now be deleted
You can now delete individual custom event occurrences directly from the Event Management tool, making it possible to clean up test events or incorrect data that previously couldn’t be removed. This helps keep reports, lists, workflows, and CRM records accurate and trustworthy. Deletions are available in-app only, support bulk deletes of up to 100 occurrences at a time, and are capped at 1,000 deleted events per month.

New Sandbox Listing Page
We’ve rolled out a redesigned Sandboxes listing page that centralizes sandbox management and production deployment tracking in a more intuitive layout. The update introduces a consolidated Sandboxes tab, a centralized activity log (covering sandbox creation details, deployments, and deletions with filtering by activity or user), and always-visible “Create a Sandbox” and “Set up a Deploy” CTAs at the top of the page. This improves information architecture and makes it faster to access sandboxes, review historical activity, and use deploy-to-production features. Availability is limited to users enrolled in the private or public beta for the new Standard Sandbox with improved production metadata and supported deploy-to-production assets.

Pre-rendering warnings now appear in Design Manager
To improve site speed, HubSpot automatically creates static versions of pages, blog posts, and knowledge base articles when possible. However, some HubL variables and functions are incompatible with pre-rendering. Before, you had to use ?hsDebugOnly=true.
Now, you can see warnings in the Design Manager about whether the page can be pre-rendered or not. Then, make changes to the code directly to address these warnings.
To opt-in to this feature, go into the Design Manager, open the Design Manager settings and toggle the Enable Pre-rendering Warnings on.

Breeze Customer Agent Now Supports Omnichannel Deployment via Custom Channels API
Breeze Customer Agent can now be deployed on ecosystem-built channel integrations, including SMS, Instagram, Telegram, LINE, WhatsApp, and Slack. Through the Custom Channels API, developers can integrate any messaging channel to Help Desk or Conversations Inbox. Customer Agent now works on any Custom Channels API channel.
What does this mean for developers?
Developers’ messaging integrations gain a powerful AI feature that makes them more valuable to customers, and any existing integration is ready to go, with no code changes necessary.
Sales and Service Hub Professional and Enterprise customers can deploy Customer Agent to custom channels.
This means your integrations can now do the following:

• The ability to assign Customer Agent to a custom channel from either the Customer Agent or channel connection setup user flows.
• Adjust customer agent handoff behavior.
• The Customer Agent responds to incoming queries on your channel.
  Note: If you are installing new channels into your existing Marketplace apps and customers have previously installed the app, you may need to ask them to re-authorize the app to grant it access to the Custom Channels API scopes.
  To get started, please refer to the documentation and explore which Marketplace app offers this functionality out of the box.

New Campaign Asset Type Associations via Campaigns Public API
We are enhancing the Campaigns API to support associations with an expanded range of campaign asset types. Developers can now programmatically add, list, or remove 11 additional asset types to campaigns, mirroring what’s possible within the HubSpot platform.
What's new?
You can now associate the following asset types with a campaign via the API:

• Ads (AD_CAMPAIGN)
• Blog Posts (BLOG_POST)
• Files (FILE_MANAGER_FILE)
• Landing Pages (LANDING_PAGE)
• Marketing Email (MARKETING_EMAIL)
• Marketing Events (MARKETING_EVENT)
• SMS (MARKETING_SMS)
• Social Posts (SOCIAL_BROADCAST)
• Video (MEDIA)
• Website Pages (SITE_PAGE)
• Workflows (AUTOMATION_PLATFORM_FLOW)
  These asset types are supported by the following API endpoints:
• Add Asset Association
• List Assets
• Remove Asset Associations
  Note: Previously, these types had to be managed via the HubSpot platform, with only a subset available through the API.
  Developers can begin reviewing and updating integrations if using custom apps or workflows to manage HubSpot campaigns, using the required asset types.
  Example payload for asset association:

{"campaignGuid":"your-campaign-guid-here","assetType":"MARKETING_EMAIL","assetId":"your-asset-id-here"}

Please refer to the developer documentation for full endpoint details.

Company Lifecycle Stage Properties
Each lifecycle stage now has four new company properties that track the company's progression through its lifecycle:

• Date entered stage
• Date exited stage
• Latest time in stage
• Cumulative time in stage
  These properties help you understand how companies move through your sales process. These company properties are automatically created for each lifecycle stage including any custom lifecycle stages created in an account.

Partner Search Analytics
App partners now have access to search analytics! This lets you track how marketplace searches enable discovery in the HubSpot Marketplace, including key metrics like:

• How often your app appears in search results (impressions)
• Which search terms lead to clicks on your listing
• Ranking position for each term (1 = top result)
  You can now monitor trends over time to understand how listing updates affect visibility.
  You can see search analytics right in your developer account under the app’s Marketplace Analytics.

Marketplace Updates
We have two quick updates for managing your app marketplace listings.
We've migrated autotranslate to our unified marketplace platform, fixing recent bugs, and improving the submission experience + end customer translations. If you already have translated listings (manually or automatically created), you won't see any changes - this update enhances reliability and streamlines new submissions.
This update will mean more reliable translations, and the autotranslate checkbox will be pre-selected, making it quicker and easier to get better translations for your listing.
We are also increasing the limit for review responses in the HubSpot Marketplace from 1 to 2. This will allow you to create 2 responses for any reviews, one to acknowledge the issue and one to notify the customer that the issue has been fixed.

Custom event updates
We have several updates for custom and app events.
Custom events created via webhooks often capture key integration data from across your tech stack, and until now, these events weren't shown in the activity timeline, didn't have the same property options as other custom events, and couldn't be edited after creation. Now, webhook Custom events function like other custom events. When a rep opens a record, they can now see any event triggered via webhook—without leaving HubSpot or running a report.
Custom events now supports the importing of event data to backfill historical data, integrate data from your tech stack with HubSpot, or capture offline behaviors you want to represent as events in HubSpot. Previously, imports could only be done as a separate, standalone event type. Now, when choosing import, you can import data to an existing event type. Additionally, imports previously only supported contact based events. Events can now be created via import for any object type Custom events supports.
We've updated the event management page to make it possible to dismiss errors for custom events. Previously, Custom event errors stay on the main event management page for 30 days, regardless of whether the issue has been resolved. Now, you can dismiss the error badge to no longer be notified about this issue for this event.
Finally, custom events and app events can be linked to several additional object types. Previously, app events and custom events could only be linked to Contacts, Companies, Deals, Tickets, and Custom objects. Both event types can now be linked to Leads, Projects, Services, Orders, Courses, Listings, and Appointments.

Public Beta: Forecast Read API
We’re excited to announce the BETA release of our Forecast Read API, available to Sales Hub/Service Hub Professional and above. This new API enables customers to access their forecast submissions from HubSpot in a structured, queryable, and read-only format—ideal for Business Intelligence (BI) reporting, analytics, and integration into data warehouses. With this release, customers can now self-serve and programmatically retrieve forecast data, advancing data accessibility and integration capabilities.
What's changing?

• Read-only API access to all HubSpot forecasts, no UI changes required.
• Structured data retrieval: Query specific fields and integrate results into BI tools or data warehouses.
• Integration-ready: Use your authenticated app (crm.objects.forecasts.read scope) to access data programmatically.
• No UI/UX changes are required: Usage is fully programmatic through the API, and there are no changes to your HubSpot account via the forecast tool.
• Beta program: This feature is in BETA. By participating, you agree to HubSpot’s Developer Terms and Beta Terms. Functionality and endpoints are subject to further development and changes.
  Usage
  Authorize your app with the crm.objects.forecasts.read and the oauth scope to use the endpoint. Below are the listed new read-only endpoints:
  Get all forecasts:
  GET /crm/objects/v3/forecasts?properties=property1,property2
  Get by ID:
  GET /crm/objects/v3/forecasts/{id}
  Example response:

{"results":[{"id":"475911884905","properties":{"hs_created_by_user_id":"2620022","hs_createdate":"2025-10-10T19:42:51.001Z","hs_lastmodifieddate":"2025-10-14T16:52:43.757Z","hs_milestone":"monthly","hs_object_id":"475911884905","hs_team_id":"39577840","hs_year":"2025"},"createdAt":"2025-10-10T19:42:51.001Z","updatedAt":"2025-10-14T16:52:43.757Z","archived":false}]}

For more details, please refer to the HubSpot API Developer Documentation.

Public Beta: Securely generate a preference page URL
The Preference Link Generation endpoints allow you to generate secure URLs to the Manage Preferences and Unsubscribe pages for any contact in your HubSpot CRM. This will allow your contacts to manage their email preferences directly from account settings or other authenticated areas of your website without requiring them to re-enter their email or dig up a past marketing email.
We've added to our Subscriptions Public APIs v4 so that you can call the new POST /communication-preferences/v4/links/generate endpoint with a contact’s email (subscriberIdString), optional language, and (for a single unsubscribe) a subscriptionId. You’ll receive secure, contact-specific links to:

• Manage Preferences page
• Unsubscribe from All page
• Unsubscribe from a Single Subscription Type page
  For more information on how it works refer to the developer documentation.

Join the discussion in the Developer Community.

Original source Report a problem

What’s Changing?

New Oauth v3 Token Endpoints

To align with OAuth 2.0 security best practices, we have introduced two new v3 OAuth API endpoints designed to keep sensitive credentials out of server logs and browser histories.

• POST /v3/token: Handles authorization code and refresh token requests.
• POST /v3/introspect: Performs token introspection, replacing the separate v1 path-based token metadata for access tokens and refresh tokens.

Standardized OAuth Error Responses

We are updating our OAuth error responses to comply with RFC 6749. This ensures better compatibility with third-party OAuth libraries and simplifies troubleshooting.

What’s changed?

Previously, responses included HubSpot-specific fields (status and message). Responses now include the standard error and error_description fields.

Example Response:

// Example Response
{
  "error": "invalid_grant",
  "error_description": "refresh token is invalid, expired or revoked",
  "status": "BAD_REFRESH_TOKEN",
  "message": "refresh token is invalid, expired or revoked"
}

Existing fields (status, message) remain for backward compatibility, so existing error handling will continue to function as is.

Important Note: These responses will be reflected in both the v1 and v3 OAuth API endpoints.

What does this mean for developers?

• Adopt v3: Start targeting /v3/token and /v3/introspect for all new developments.
• Update Request Logic: Ensure your application sends credentials in the request body, never in the URL.
• Error Handling: You can now update your client-side error handling to parse standard OAuth error fields.

Important note: There are no changes to the scope, app settings, or the OAuth install process.

Sunset Notice for v1 OAuth API Endpoints

The v1 OAuth API endpoints will remain operational for now, but they are officially deprecated. We will provide a detailed sunset timeline later in Q1 2026. Please subscribe to the HubSpot Developer Changelog to ensure you receive this update.

When is it happening?

The v3 OAuth API endpoints are now available for use, and the error standardization is now reflected in both the v3 and v1 OAuth API endpoints.

Questions or comments?

Join us in the developer forums for a peer-to-peer discussion.

Original source Report a problem

What’s changing

HubSpot CLI v8.0.0 is a major release focused on maintenance and cleanup. It removes long-deprecated functionality and aligns the CLI with previously announced platform changes.

Node.js requirements

• The minimum supported Node.js version is now Node 20
• Legacy behavior for hs theme preview on Node versions lower than 20 has been removed

This follows prior guidance:

• In April 2025, we announced an October target for deprecating Node 18 in all serverless functions and the CLI

Deprecated commands removed

Commands deprecated in favor of the newer hs cms, hs app, and updated command structure have now been fully removed. This follows the command reorganization announced in October 2025.

Removed command Replacement command hs create hs cms app hs fetch hs cms fetch hs function deploy hs cms function deploy hs function list hs cms function list hs function server hs cms function server hs lint hs cms lint hs list hs cms list hs logs hs cms function logs hs module marketplace-validate hs cms module marketplace-validate hs mv hs cms mv hs remove hs cms delete hs theme generate-selectors hs cms theme generate-selectors hs theme marketplace-validate hs cms theme marketplace-validate hs theme preview hs cms theme preview hs upload hs cms upload hs watch hs cms watch

Custom object schema command changes

The following legacy commands have been removed in favor of updated equivalents:

Removed command Replacement command hs custom-object schema create hs custom-object create-schema hs custom-object schema delete hs custom-object delete-schema hs custom-object schema fetch-all hs custom-object fetch-all-schemas hs custom-object schema fetch hs custom-object fetch-schema hs custom-object schema list hs custom-object list-schemas hs custom-object schema update hs custom-object update-schema

Additional breaking changes

• Removed support for 2023.2 projects
  • Creating 2023.2 projects via hs project create is no longer supported
  • Migrating legacy apps to 2023.2 using hs app migrate is no longer supported
• Removed deprecated command:
  • hs project clone-app
• Removed support for the HUBSPOT_PORTAL_ID environment variable
  • Use HUBSPOT_ACCOUNT_ID instead

Bug fixes and improvements

• Fixed an issue where CLI versions > 7.9.0 did not work with the --use-env flag
• General refactoring and cleanup tied to deprecated functionality removal

For full release details, see the GitHub release notes:
https://github.com/HubSpot/hubspot-cli/releases/tag/8.0.0

CI/CD considerations

This release does not force an immediate upgrade to HubSpot CLI v8.0.0. However, CI/CD pipelines may be affected once this version is adopted.

In particular, we recommend reviewing the following in automated environments:

• Environment variables
  • Replace usage of the deprecated HUBSPOT_PORTAL_ID environment variable with HUBSPOT_ACCOUNT_ID
  • This variable is commonly set in CI/CD workflows and is no longer supported in v8.0.0
• GitHub Actions
  • If you are using version 1 of the HubSpot CMS Deploy GitHub Action, upgrade to v1.8
  • Earlier versions install the latest version of the HubSpot CLI, which may pick up breaking changes
  • Version 1.8 pins installation to the latest v7 CLI release to avoid unexpected breaks
• CLI command usage
  • Review pipeline scripts for deprecated or removed CLI commands
  • Update command references to their supported replacements before adopting v8.0.0

When is it happening?

This change goes into effect on February 9, 2026.

Questions or comments?

Join us in the developer forums.

Original source Report a problem

Ecosystem partners and customers can now build and manage their own AI connectors to the (Beta) HubSpot Remote MCP (Model Context Protocol) Server through a streamlined self-service interface. This public beta builds on the initial release of the HubSpot Remote MCP Server and simplifies the experience of creating and managing AI connectors directly.

What’s Changing?

A new MCP Auth Apps UI has been added to the HubSpot Developer Platform to allow ecosystem partners and customers to build and manage their own AI connectors to the HubSpot Remote MCP Server through a streamlined and fully self-service experience.

An earlier public beta, released on September 1, 2025, introduced the HubSpot Remote MCP Server available across all hubs and tiers. However, connector creation and management still relied on other platform developer tools intended for apps providing more functionality in HubSpot.

With this update, partners and customers can independently manage the full connector lifecycle using the new UI, including:

• A dedicated MCP Auth Apps section in the HubSpot Developer Platform
• Creating new MCP connectors through a self-service interface
• Modifying and maintaining connector settings through the UI
• Securely access their OAuth 2.1 credentials for integrating external systems with the HubSpot Remote MCP Server

End-user installation permissions for these apps are now managed automatically, giving customers full control over what HubSpot data they share via the MCP server connection without requiring partners to manually configure or manage permissions.

For implementation details, see the developer documentation.

When is it happening?

• The initial public beta for the HubSpot Remote MCP Server went live on September 1, 2025.
• A new public beta for self-service connector creation and management using the MCP Auth Apps UI for ecosystem partners and customers went live on January 13, 2026.

Questions or comments? Join us in the developer forums.

Original source Report a problem

This month’s updates focus on enhancing developer workflows and platform security, featuring a new IP Ranges API for firewall management and the general availability of the App Uninstallation API. We’ve also introduced several quality-of-life improvements, including a Legacy CRM Card Converter to assist in your migration to modern App Cards, setting a custom template for CPQ quotes, actionable migration insights directly within your HubSpot Account, and expanded Breeze Assistant capabilities for custom website and app event data. Finally, wer'e making significant updates to the standard sandbox experience that bring predictable record limits and new deployment capabilities.

New Resource: Legacy CRM Card Converter

To support developers migrating from Classic CRM Cards to the new App Cards, we’ve released the Legacy CRM Card Converter, a lightweight tool and example designed to simplify the transition process. The resource provides:

• Sample mappings that demonstrate how Classic CRM Card patterns translate to modern App Cards.
• Reference implementation to help you quickly understand equivalent React-based structures.
• Guidance and best practices for updating legacy cards to transition to new UI Extension capabilities.

The card converter is intended to accelerate planning and development as you prepare for the October 31st, 2026, sunset of Classic CRM Cards. Explore the tool here: https://github.com/HubSpot/ui-extensions-examples/tree/main/legacy-card-converter

Developer Tasks and App Migration Paths

Now the Developer Platform surfaces actionable insights directly on the Developer Overview for all HubSpot Accounts. Developers can view task cards highlighting whether any of their apps are eligible for migration to the new Developer Platform, with clear guidance on which apps can and cannot be migrated.

• Task Cards: A task card lists action items for developers, focusing on highlighting eligible apps for migration. A task card can be found on the Developer Overview page within the HubSpot Account.
• Migration Eligibility Labels: Each app is now labeled as ‘Yes’ (can be migrated) or ‘No’ (should not be migrated). When migration steps are available, developers will be directed to the Legacy Apps page within your HubSpot Account.

Previously, the Developer Overview lacked actionable next steps, leaving users uncertain how to maintain or upgrade their apps. These new insights enable clear, actionable guidance, reducing mistakes and improving the migration experience. For additional guidance, refer to the Developer Platform documentation on app migration guides.

HubSpot IP Ranges API

You can now dynamically access HubSpot's public IP ranges for your projects and firewalls. With this API, you can automatically update your firewall rules and enhance your security monitoring. You can retrieve the set of IP ranges using this endpoint:
https://api.hubapi.com/meta/network-origins/2025-09/ip-ranges
This API does not require authorization. The response will include a list of IP ranges and the HubSpot services using those IPs. See the documentation for full details.

New Filter by Object Type ID for v3 Lists API

The /crm/v3/lists/search endpoint in the v3 Lists API now supports filtering lists by object type using the objectTypeId parameter in the POST request body. See additional details on what specifically changed, below:

• New Filter Option: Developers can now include the objectTypeId property in the POST request body when querying the /crm/v3/lists/search API endpoint.
• Supported Values: Common values include object type IDs, such as "0-1", or a string, such as "CONTACT".
• Request Body Example:

{
  "query": "HubSpot",
  "processingTypes": ["MANUAL"],
  "objectTypeId": "0-1"  // "CONTACT" also works
}

This new feature enhances list segmentation by allowing filtering of lists by HubSpot CRM object type. Applicable to CRM segments (part of Lists), especially for Marketing Hub and Main Hub products. Additionally, this change enables tighter integration for custom reporting and workflow automation with more granular access when programmatically dealing with lists for marketing and CRM operations.

Template Selection for CPQ Quotes via API

You can now specify a custom template when creating CPQ quotes through the Quotes API, rather than relying on the default content template. This unlocks full control over quote design and structure for any workflow that programmatically generates quotes. During creation, the API will associate the quote to the selected template and pull in any additional template data, while still prioritizing values explicitly set on the quote. Note that templates can only be chosen at creation time and cannot be changed after the quote is generated. Learn more in the Quotes API documentation.

Standard Sandbox Updates: New Limits, New Capabilities, and Legacy Sunset

HubSpot is rolling out a more powerful Standard Sandbox experience, alongside clearer data limits and a planned sunset of Legacy Standard Sandboxes.

• All sandboxes will now enforce a consistent limit of 200,000 records per major CRM object type (including contacts, companies, deals, tickets, custom objects, and more), ensuring predictable performance and stable testing environments.
• In parallel, a new Standard Sandbox version introduces an enhanced copy of supported production metadata and a Deploy to Production feature for eligible assets, enabling teams to safely test and then natively deploy schema changes, workflows, lists, forms, and automated emails.
• To support this upgrade, Legacy Standard Sandboxes will be sunset on March 16, 2026, fully replaced by the new Standard Sandbox. Super Admins can create the new sandbox now, with temporary sandbox limit increases available to ease migration; no action is required until the sunset date, but customers with connected apps or complex automations should plan ahead. Learn more in the Sandbox FAQ and documentation. Read more regarding the sunset on the dedicated changelog post which includes helpful FAQs.

Public API for Uninstalling an app released to GA

The previously announced API for uninstalling an app from a HubSpot Account has been released from beta into general availability. This endpoint allows app builders to remove their app from a HubSpot Account, which removes any app features set up for the app, including removing any configured app cards, as well as unsubscribing any configured webhooks for that account. See the documentation for more details.

Updates to associations to the Cart object

You can now create associations between carts and custom objects, and configure custom association labels and limits for the cart object. This improvement allows you to tailor the cart object to your specific business needs and workflows. This update allows integrations to update associations using the Associations API, as well as allowing super admin users to update associations by editing the data model in their account. Additionally, users can associate carts to deals directly from record pages in HubSpot.

Breeze Assistant can now query your Custom event and App event data

Breeze Assistant can now query the custom website events and app events you've configured in your HubSpot Account. You can now get answers about these events directly from Breeze Assistant, helping you:

• Gain deeper insights into user behavior on your website and through your apps.
• Make data-driven decisions based on specific actions your customers are taking.
• Streamline your ability to answer important questions about your business using these additional data sources.
  This enhancement brings you closer to having a comprehensive view of all your HubSpot data through Breeze Assistant. No additional setup is required to enable this functionality. Once you've configured these events in your HubSpot Account, you can ask Breeze Assistant questions about your custom website or app events.

Questions or comments?

Please join us in our developer forums.

Original source Report a problem

What This Means for You

To support this change, your sandbox limit will be temporarily increased so you can create and configure a new standard sandbox while still accessing your legacy sandbox.

• Most customers will experience minimal impact.
• Teams with connected apps that orchestrates data flow across systems may need to review and reconnect certain elements in the new sandbox.

The new standard sandbox includes:

• A more accurate representation of the most requested supported asset types
• A new Deploy to Production feature for supported asset types

FAQ — What You Need to Do Before March 16, 2026

Who can make these changes

Any Super Admin can create a new standard sandbox and delete the legacy one. We recommend coordinating with the Super Admins who actively use sandboxes and maintain integrations to assess the requirements.
If you have questions not answered in this FAQ please reach out to your Customer Success Manager or visit the HubSpot Help Center.

How to assess your migration needs

1. Create your new Standard Sandbox
   Your temporary sandbox limit allows you to create it without deleting your legacy sandbox.

2. Review whats in your Legacy Sandbox
   Identify any integrations, apps, or automations your tech stack depends on, for example:

• Connected private or public apps
• Workflows that send data externally through webhooks
• Custom-coded workflow actions

1. Recreate or reconnect what you need
   If you use integrations or apps, you may need to:

• Reconnect private and public apps
• Update authentication or secrets in integrations settings and workflows with webhooks

1. Validate your setup in the new sandbox
   Ensure integrations, authentication, and any data-flow-related logic are functioning correctly by comparing them against your legacy sandbox or requirement documentation.

2. Delete your Legacy Sandbox
   Once your new sandbox is fully operational, delete the legacy sandbox. Your temporary sandbox limit increase will be removed.

What happens to legacy sandboxes on March 16, 2026

If you don’t migrate before March 16, you will lose access to your legacy sandboxes. After that date, only the new Standard Sandbox will be supported.

Who Is Impacted

Most Customers (Simple Testing Use Cases)

Most teams will experience minimal impact and can simply:

1. Create a new standard sandbox
2. Confirm no migration needs exist
3. Delete their legacy sandbox

Customers Using Private/Public Apps

If your sandbox connects to external systems, expect a deeper review. You may need to:

• Assess and reconnect private or public apps
• Refresh authentication tokens, secrets, scopes
• Update references to your new sandbox’s account ID
• Review workflows that contain webhooks or custom-coded actions
• Once validated, you can delete your legacy sandbox

Why We’re Making This Change

Legacy sandboxes were foundational, but they had key limitations, especially around tracking changes critical for supporting safe, predictable deployments to production.
The new Standard Sandbox addresses these challenges with:

A production-like environment for supported assets

• A more accurate representation of supported assets, allowing you to test confidently without disrupting live systems or your end users in production.

A native Deploy to Production experience for supported assets

• You no longer need to rebuild supported assets manually once testing is complete. The new deployment technology provides:
  • Predictable, safer deployments
  • Visibility into eligible assets and required connected assets
  • Conflict warnings
  • Deployment logs for transparency and troubleshooting

Why the legacy resync feature is removed

Although the resync feature felt useful, it introduced major instability in sandbox development. It could overwrite in-progress work, break change tracking, disrupt reliable development practices, and increase the risk of errors when deploying changes to production. Removing resync eliminates these risks and ensures sandboxes remain clean, consistent environments you can trust.

How to get a fresh copy of production

To maintain a reliable development environment, your sandbox should be recreated, not resynced, whenever you need a fresh copy of production. Recreating your sandbox eliminates drift, restores a clean baseline, and ensures that what you test behaves the same way in production.
This change makes deployments more predictable and aligns our process with industry standards for managing development environments and deploying tested changes to production safely.

How to Manage Your Sandboxes Going Forward

To get you started adopting this new way of working with the delete and create model consider implementing lightweight governance practices such as:

• Defining when a sandbox should be recreated
• Assigning clear ownership and access
• Keeping sandboxes purpose-driven and uncluttered
• Deploying changes intentionally, not reactively

Together, these practices support safer deployments, reduce operational risk, and clarify how sandboxes should be managed across your organization. Here’s a framework to help you get started.

Checklist for Customers with Connected Apps

If your legacy sandbox has connected apps, review the following when assessing configuration requirements in your new standard sandbox:

Account IDs

• Each sandbox has a unique ID. Update any systems that reference your legacy sandbox’s ID.

API calls, authentication, and secrets

• Generate new credentials in your new sandbox and update external systems if needed.

Private & Public Apps

• Private apps: reconnect and generate new tokens (Developer docs here)
• Public apps: reauthorize following developer documentation here

Workflows with Webhooks or Custom-Coded Actions

• Review and update webhook and custom-coded actions
  • Update authentication types (KB article here)
  • Re-enter endpoint details

CRM Data Imports

If you test data flow across systems, you may need to reimport CRM records.
Because record IDs differ between production and sandbox, consider using a consistent identifier:

1. In Production: Create a custom property (e.g., “external ID”)
2. In Production: Use a workflow to copy record IDs into this property
3. In Sandbox: Use this external ID to upsert records

Next Steps

If you haven’t already, the best next step is to create your new Standard Sandbox and review what may need to migrate. Most of the work will be straightforward, and if you have integrations, a bit of early review ensures a smooth transition.

Final Thoughts

We know this change represents a shift in how you’ve used sandboxes in the past. We’re sharing it early to give you clarity and confidence throughout this transition.
The improved Standard Sandbox, with its production-like environment and Deploy to Production, helps you build, test, and deploy changes the way modern teams should: safer, more predictable, and more efficient.

Questions or concerns?

Join us in the Developer Community Forum for a peer-to-peer discussion.

Original source Report a problem