Skip to main content Skip to footer

HubSpot Developer Changelog

Fall Spotlight 2025: New & Improved HubSpot APIs

The HubSpot public APIs are the foundation for extending the power of the Smart CRM to wherever our customers do business. As we remain committed to improving developer productivity, we’re improving and expanding upon our suite of public APIs to build integrations for HubSpot. From more third-party connectors to a new date-based versioning system, we’re excited to let you know about the recent updates we’ve made to bring HubSpot everywhere.

Date-based Versioned APIs Are Coming

Over the next several months, we’ll be rolling out date-based versioned APIs into beta across our catalog of APIs. This calendar-based versioning ensures you know you’re using the most up-to-date endpoints, and you can better plan for future updates with fewer interruptions.

So, instead of using v3 of the HubSpot CRM APIs, you would use the 2025-09 version. This allows us to roll out changes on a set release cadence and standardize versioning across our suite of APIs. Currently, we've released the beta date-based version APIs for CRM objects, properties, associations, and account info.

We’ll continue to support the numerical versions of our APIs as we gradually roll out date-based version APIs. Continue to subscribe to the HubSpot Developer changelog for ongoing updates to all of our APIs.

Updates to Our Current Public APIs

After releasing the Commerce Hub Payments API and Campaigns API, we’ve continued to improve their capabilities.

The Commerce Hub Payments API now supports full CRUD (create, read, update, delete) operations for payments. New endpoints have been added for:

  • Creating payments
  • Updating existing payments
  • Associating payments with invoices, subscriptions, and deals

For full details, please read our changelog.

The Campaigns API has been updated to bring it closer to feature parity with the HubSpot platform, providing greater flexibility and control for developers.

These updates include:

  • Expanded support for a wider array of asset types
  • New endpoints for managing campaign budgets and spend
  • Added support for custom UTM property read/write capabilities
  • Additional business unit data to Campaign GET responses
  • Enhanced scope requirements

For full details, please read our changelog overview and our changelog announcement on scope enhancements and property deprecation.

More Features for Inbound Calling

We’ve also made improvements to the Calling Extensions SDK. These features are in beta and include inbound calling support for third-party integrations. Now, users can receive inbound calls from any page within the CRM.

With these improvements to the Calling Extensions SDK, third-party inbound calling features can also be integrated into Help Desk. Help Desk users will be able to receive incoming calls through the integrated app. When a call is answered, a ticket is automatically created, allowing support reps to begin working on it in real time.

Read more about how to integrate your third-party calling platform with Help Desk in our developer docs.

Lastly, we’ve released a transcription API into beta. If you use a third-party solution for transcribing calls, you can sync those transcriptions to HubSpot using this API. Learn more about using the third-party transcription API on our developer docs.

API Updates for App Partners

For our app partners, we’ve released a brand new public API to uninstall customers from your app. On a successful request, the app will be removed from the account, and the account admins will receive an email notification that the app has been uninstalled.

The email will be sent to all Super Admins for the account, and will include a link to the app's connection page, allowing admins to reinstall the app if the uninstall was unintentional or if they wish to reinstall the integration. You can read more about this new endpoint on our changelog.

Finally, the limits for the custom event completions API have increased to help you deal with more signals from more places.

  • The send custom event completion endpoint now supports up to 1,250 requests per second.
  • The custom event completion batch endpoint now supports batches of 500.
  • Reports built in the custom report builder now support viewing 10 years of event data for all event types, including custom events.
  • These rate limit changes are automatically applied to all Enterprise customers.

As our platform grows, we’re excited to continue to iterate and expand on our API offerings to help you drive faster value for customers and solve pain points wherever they may arise. Happy building!

Have questions or feedback? Join our developer community for a peer-to-peer discussion.