HubSpot Ends Legacy Private-App Creation for New Accounts Sept. 28

HubSpot says accounts created on or after September 28, 2026, can no longer create legacy private apps. For a sales operations team building a custom CRM connection, the account’s creation date now determines whether that option is available: accounts created before September 28 have until October 26, 2026, to create one.

This is a cutoff for creating legacy private apps, not a shutdown of apps already in use. HubSpot recommends service keys for account-level API integrations. If the connection needs webhooks or UI extensions, a service key cannot authenticate those features; the team needs an app.

Check permissions before choosing a service key

Service keys remain in public beta and provide scope-limited access to HubSpot’s REST APIs. Super admins and users with Developer tools access can create and manage them. HubSpot says a key’s scopes cannot exceed its creator’s access, giving teams a defined permission boundary for API calls.

HubSpot’s documentation also describes request logs and two choices when rotating a key: immediate expiry or a seven-day overlap. The creation cutoff is defined by account date; the service-key documentation specifies user permissions but does not establish beta eligibility by Free, Starter, Professional or Enterprise plan. Teams considering that route should confirm access in their own account.

Existing apps face a separate deadline

In a later support schedule, HubSpot says legacy private apps must migrate to its Projects-based model by September 2027. That is separate from the September 28 creation restriction for new accounts and the October 26 cutoff for older ones. Teams can choose credentials for new API connections now while identifying existing legacy apps that need a migration plan.