v1 OAuth API Deprecation
HubSpot is deprecating the legacy v1 OAuth API in favor of a new date-based, versioned OAuth API for token issuance and introspection. The v1 API will be fully deprecated on February 16th, 2027, and a new REVOKE endpoint is being introduced in the latest OAuth API version.
We have introduced the latest date-based, versioned OAuth API for token issuance and introspection, as announced previously here. As adoption of the new OAuth API grows, we are beginning to deprecate the legacy v1 OAuth API. As part of this transition, a new REVOKE endpoint is also being introduced for the latest date-based versioned OAuth API, and the v1 API will be fully deprecated on February 16th, 2027.
Source: original entry ↗
More from HubSpot
Follow HubSpot to get its new changes in your feed and email digest.
HubSpot-hosted domains moving to TLS 1.2 minimum
HubSpot will automatically update the minimum TLS version for HubSpot-hosted domains from TLS 1.0 or 1.1 to TLS 1.2 on October 14th, enhancing security for all hosted domains.
End of Support for v1-v3 APIs and Legacy Apps
HubSpot is ending support for v1-v3 APIs, legacy public apps, and legacy private apps effective September 2027. Customers and partners have a 12-month window from the announcement to migrate to supported alternatives.
Fall 2026 Spotlight - Developer and Builder Updates
HubSpot's Fall 2026 release introduces new features on Developer Platform 2026.09, including updated APIs, new beta APIs, and AI builder tools. This changelog covers non-breaking updates; see the separate breaking changes article for legacy API deprecations.