At Fall Spotlight on September 15, HubSpot is announcing the end of support for v1-v3 APIs, legacy public apps, and legacy private apps, all with a September 2027 enforcement date. If your integration or app uses any of these, you have a 12-month window to migrate.
This changelog covers v1-v3. Support for v4 is ending on its own separate timeline, March 30, 2027, which was announced earlier this year. See the previously published v4 changelog for that timeline.
This post covers breaking changes only. For everything new and non-breaking in this release, including the APIs reaching general availability, the updated APIs, the new public betas, and the latest AI builder tools, see the Fall Spotlight 2026 developer rollup.
Three simultaneous announcements share the same enforcement date: September 2027.
Endpoints using numbered version paths, /v1/, /v2/, and /v3/, will move to unsupported status. HubSpot will no longer release bug fixes, reliability improvements, or security updates for these versions. After September 2027, these endpoints will be unsupported. (Support for v4 is ending separately on March 30, 2027, announced earlier this year. See the v4 support timeline.)
Migrate directly from any legacy version to date-based versioning (DBV). Do not use v3 or v4 as an intermediate step. See the DBV migration guide for the full process, including endpoints where the response shape changes, not just the URL path.
Public apps created before June 23, 2026 use HubSpot's pre-Projects app architecture. These apps move to unsupported status on September 15, with enforcement in September 2027. To remain listed in the Marketplace and retain certification, migrate to the current Projects-based app model. See the app migration guide.
Private apps built before the Projects-based private app model was introduced must also migrate to Projects-based private apps by September 2027. This is a separate announcement from the public app change.
If you're building a new private integration, use Service Keys (now available) instead of creating a new legacy private app. Service Keys are the recommended path for lightweight integrations, internal tools, and AI agent integrations, with no full OAuth backend required. See the Service Keys documentation.
Note: legacy private app creation is disabled on September 28, 2026 for new accounts and October 26, 2026 for existing accounts.
Apps in the HubSpot Marketplace must meet both requirements to remain listed and retain certification. They apply independently, so you need to address both.
An app that has migrated to Projects but still calls v1-v4 APIs is still at risk of losing certification. An app using date-based APIs but still on legacy app architecture is still at risk of delisting.
| Date | Milestone |
|---|---|
| September 15, 2026 | All three changes announced; 12-month migration window opens |
| September 28, 2026 | Legacy private app creation ends for new accounts |
| October 26, 2026 | Legacy private app creation ends for existing accounts |
| September 2027 | Enforcement; legacy APIs unsupported, legacy public apps and private apps also unsupported |
Starting September 15, the developer home tasks card is the fastest way to see your specific impact. Migration guides are available for API versioning and app architecture.
Questions? Join the migration discussion in the developer forums.