HubSpot will disable new legacy private app creation starting September 28, 2026
HubSpot said on August 27, 2026, that it will permanently remove the account UI path for creating new legacy, non-Project based private apps, with new accounts affected on September 28 and existing accounts affected on October 26. The notice appeared in HubSpot’s developer changelog and a matching Developer Community announcement, while a third-party software changelog tracker also logged the move the same day. Existing legacy private apps continue to work, but new in-account API integrations are being pushed toward Service Keys and project-based apps.
HubSpot legacy private app creation gets September 28 and October 26 cutoff dates
The cutoff is tiered by account age. HubSpot accounts created on or after September 28, 2026 will lose the ability to create new legacy private apps on September 28. Accounts created before September 28 will keep that creation option until October 26, 2026.
The important nuance is that HubSpot is not revoking existing legacy private app tokens as part of this announcement. Existing legacy private apps remain active, so current integrations should not break simply because of the policy change. The change affects the creation path, not the runtime behavior of apps already in place.
In practice, the bigger disruption is operational. Many RevOps, data, and IT teams still use legacy private apps as the fast route to generate a scoped access token for a report, sync job, middleware script, or one-off integration. After the relevant cutoff date, that familiar Settings UI workflow will no longer be available for new legacy private apps.
Service Keys become HubSpot’s path for data-only API integrations
HubSpot is steering new in-account API work toward Service Keys, which it describes as account-level credentials for system-to-system, data-only integrations. The earlier HubSpot explanation of Service Keys for data integrations positions them as the cleaner replacement for cases where teams mainly need stable API access rather than a full app lifecycle.
That distinction matters. A reporting pipeline that pulls contacts into a warehouse, a scheduled script that updates deal properties, or a BI connector that only needs read access is the kind of workflow Service Keys are built to handle. HubSpot says Service Keys support scoped access, built-in activity logging, key rotation with a 7-day grace period, and admin-only key visibility.
The security posture is stronger than the old habit of creating a private app token and letting it live indefinitely in a spreadsheet, middleware account, or environment variable nobody reviews. The trade-off is that teams need to adjust their internal documentation and onboarding patterns. Any runbook that says create a private app, copy the token, and paste it into the connector now has a firm expiration date.
Project-based HubSpot apps remain required for webhooks and UI extensions
Service Keys are not a full replacement for every legacy private app pattern. HubSpot’s own Service Keys guidance says webhooks, UI extensions, app pages, and Marketplace distribution remain in the project-based app lane. That means integrations with event subscriptions, CRM cards, custom app pages, or customer-facing distribution still need the newer app framework rather than a Service Key.
This is where some teams may feel the migration most sharply. A legacy private app used only as an API credential can usually move cleanly to a Service Key. A legacy app that also represents a broader integration pattern may need to be rebuilt or formalized as a project-based app.
HubSpot’s developer platform documentation still says legacy private and public apps are supported and that REST APIs remain available through private app access tokens or public app OAuth tokens. The August 27 announcement narrows the future creation route, while leaving the existing support story largely intact for apps already created.
HubSpot 2026.09 developer platform changes now reach admin workflows
The timing lines up with HubSpot’s broader move toward a more structured developer platform. HubSpot’s developer platform and API versioning documentation says new REST API and app developer platform versions are generally available every six months, in March and September, with versions moving through current, supported, and unsupported stages.
That makes the private app creation cutoff more than a small UI removal. It is another step away from ad hoc portal-based app creation and toward managed credentials, project-defined apps, and clearer platform version boundaries.
For admins, the near-term implication is straightforward: existing legacy private apps can continue running, but new integration plans need to choose the right replacement path before the cutoff dates. Data-only jobs fit Service Keys. Anything involving webhooks, UI components, app pages, or distribution belongs in project-based apps. The risk is not that HubSpot turns off existing integrations overnight. The risk is discovering after September 28 or October 26 that a familiar setup path no longer exists when a new portal, client account, or internal project needs it.
Share With Others
Platinum
