November brings a rollup with several updates across the platform. We've expanded record limits for Orders and Carts objects, increased association limits fivefold to 250,000 per object type, and launched the new Projects API for programmatic project management. We're also introducing property validation rules via the public CRM API, releasing HubSpot CLI 7.10.0 with dependency updates and enhanced MCP tooling, and rolling out flexible header and footer switching in the CMS. On the governance front, we're sharing the Platform Lifecycle Management schedule for proactive planning, implementing new user-level permissions requirements for AI connectors on the Marketplace, and enhancing our documentation with required scopes, object definitions, and searchable changelog entries. We've also got important reminders about upcoming API sunsets for Clearbit Logos and Contact Lists v1. Make sure to read on to find out more about each of these updates.
We are excited to announce that the Orders and Carts objects have new record limits:
A reminder that the deprecated Clearbit Logo API (logo.clearbit.com) will be shut down on Dec. 8, 2025.
If you are still using this service, we recommend that you use another alternative, such as logo.dev, a free and high-quality logo-fetching service based on domain names. Learn more about migrating to a different service on our Clearbit Logos API sunset announcement.
The v1 Contacts List API is slated for sunset on April 30th, 2026. Please refer to this announcement for more details on the sunset and migration options.
You can now create, update, and retrieve property validation rules through the public CRM API. This allows developers to enforce data consistency and integrity programmatically—for example, requiring specific formats, minimum lengths, or character types for property values. Use the new endpoint crm/v3/property-validations/{objectTypeId}/{propertyName}/rule-type/{ruleType} to define or fetch validation configurations. Learn more in the Property Validations API documentation.
HubSpot CLI 7.10.0 delivers a substantial upgrade to the developer experience with the introduction of hs project update-deps, a new command that streamlines updating npm dependencies across project components. This provides a clearer, safer workflow for keeping project libraries current without reinstalling from scratch. The release also adds support for beta platform versions, enabling developers to experiment with upcoming HubSpot platform capabilities before they reach general availability.
This version includes notable improvements to MCP tooling, including codex integration for setup, message and profile support for MCP project uploads, and enriched debugging output that now surfaces network request context to make troubleshooting smoother. File handling has also been refined—particularly around markdown file collisions—to ensure documentation remains intact during renames.
On top of these enhancements, developers will find numerous quality-of-life and reliability fixes, from resolving require.resolve() issues in CMS theme previews to improving dependency-related error messages, flag handling, and package-installation utilities. These updates maintain complete backward compatibility while meaningfully modernizing core workflows.
Watch the new test account creation walkthrough video and check out the full set of changes on GitHub.
HubSpot has raised association limits for all paid accounts, allowing individual records to be linked with up to 250,000 records of a given object type (for example, 250,000 contacts with a single company). This fivefold increase expands your ability to model large and complex data relationships directly in HubSpot, including via API and imports. Some object-specific limits still apply—for instance, 10,000 associated deals per contact and 1,000 associated records per engagement. Learn more in the Associations API documentation and review the HubSpot Product & Services Catalog for full details on technical limits.
You can now choose a separate header or footer module per page in the HubSpot Elevate theme. Previously, headers and footers were universal across templates, meaning you had to switch out the template to use a different header or footer per page. This meant that you had duplicate templates with different headers or footers.
Now, you can switch out the header or footer directly from the page editor. When you hover over a header or footer, you'll be able to open up a modal to replace the current page's header or footer. This will not affect other pages using this same template, only the page you're currently editing.
This update allows you to have individual headers on footers on pages while re-using the same templates, giving you flexibility across your website, including across different brands.
HubSpot launched the Platform Lifecycle Management with the Developer Platform, providing a public schedule for project platform version release, support, and deprecation timelines in the developer documentation. This transparency allows developers to proactively plan updates, avoid breaking changes, ensure app stability, and improve end-user reliability. Developers will also receive proactive release and deprecation notifications via the HubSpot CLI, UI, and email. See the developer documentation for the complete schedule.
AI connectors are defined as apps that primarily connect HubSpot directly to general-purpose generative AI assistants or agents. Due to the importance of user-level permissions to customer data security and privacy in AI systems, we require all new AI connectors on the Marketplace to support user-level permissions via the HubSpot Developer Platform.
To list an AI connector on the HubSpot Marketplace, developers must rebuild their app using the official HubSpot MCP server (BETA), which enforces user-level permissions. Only CRM read operations are currently available.
AI connector apps that do not wish to rebuild using the official HubSpot MCP server can continue to distribute their app and drive installs outside the Marketplace. For this alternative, it is important to be aware of the new active install limits for unlisted apps using the HubSpot Developer Platform as outlined in this Developer Changelog post.
No additional action is required for customers beyond installing compliant apps; enforcement is applied by Ecosystem Quality via the App Listing Requirements.
These requirements maintain the same user-level access guardrails implemented in our own connectors. When HubSpot designed and built its own connectors, such as the HubSpot connector for ChatGPT, we built them to enforce user-level access from the beginning (learn more in this blog post). This model ensures that any action taken by an AI assistant or agent on a user's behalf is strictly limited to that specific user's existing permissions within HubSpot, preventing unauthorized data access and maintaining compliance.
The Projects API is now available in support of HubSpot's new recently launched project object. With this new API, customers and partners can programmatically create, read, update, and associate projects to related records. The Projects API will be available through HubSpot's CRM Objects API framework. See the documentation for more details.
There are several documentation improvements to streamline how you discover and use information in HubSpot's developer documentation:
Required Scopes in API Reference Docs: A new, dedicated component now lists the application scopes needed for each API endpoint. This helps you quickly confirm permissions and avoid authentication issues when building or updating integrations.
[In beta] Object definition pages for key CRM objects: Selected APIs now include "Object definition" pages to make it easier to understand object structure, find available default properties, and troubleshoot data sync issues. Highlights include:
Changelog Entries Shown in Docs Assistant: You can now see recent developer changelog entries directly in documentation assistant results. This means you'll instantly spot any updates affecting the endpoint you're exploring, helping you adapt to changes faster and with greater confidence.
Collectively, these enhancements are designed to reduce friction—helping you identify needed scopes, understand object models, and monitor relevant updates with less guesswork.
HubSpot now enables publishing Call Started and Call Ended events for third-party calls. These events are not only logged but can also be leveraged in Journey Analytics and Workflows, making call data actionable across the platform.
To ensure these events are published correctly, integrators need to send the following SDK events: incomingCall, callEnded, and finalizeEngagement. For full implementation details, refer to the API documentation.
Questions or concerns? Join us in the Developer Community Forum for a peer-to-peer discussion.