Service Keys are now available in public beta as a new authentication option for account-level, system-to-system integrations. This feature is intended to replace legacy private apps and is built on HubSpot’s modern Developer Platform infrastructure.
Service Keys introduce a simplified way to create and manage API credentials without building a full app, while maintaining strong security and access controls.
Service Keys are designed specifically for:
As part of this release, Service Keys are replacing functionality legacy private apps served. Service Keys should be used going forward.
Service Keys are intended to replace legacy private apps where:
Service Keys do not support webhooks. If your integration requires webhooks, you must use a project-based app created with the HubSpot CLI, or continue using a legacy private app.
Legacy private apps remain available for now, but customers building new system-to-system integrations should use Service Keys.
Service Keys follow a permission model aligned with existing account access:
This ensures users cannot escalate privileges beyond their existing permissions.
When a Service Key is created, Integrations continue to function even if the original creator leaves the account. Admins retain access to the Service Key and API access is not tied to an individual employee.
Service Keys can be found at Settings > Integrations > Service Keys or by navigating to Development > Keys > Service Keys from the main sidebar.
Admins can:
Service Keys do not support all app capabilities.
Learn more about Service Keys and other methods of authentication in the Developer Documentation.
This feature is available in public beta starting February 10th, 2026.
Questions or comments? Join us in the developer forums.