On this page
What HubSpot supports natively
As of October 29, 2026:
| Legacy private app | Service key | |
|---|---|---|
| Create new | No (disabled September 28, 2026 for new accounts, October 26, 2026 for existing) | Yes: Development → Keys → Service keys |
| Existing ones | Keep working | |
| Scopes | Object-specific, edited on the Scopes tab | Object-specific, editable after creation |
| What it can call | REST APIs | REST API requests only; no webhooks or UI extensions |
| Rate limits | Privately distributed app limits | Same as privately distributed apps |
| Who can create | Super Admin | Super Admin or Developer tools access permission |
Service keys can also rotate automatically every 3, 6 or 12 months. Scopes depend on what the account includes: if the account has no HubDB, no credential gets the HubDB scope. An account can hold 100 project-based apps, service keys and MCP connectors combined.
How to choose HubSpot private app scopes (or service key scopes)
Scopes follow a pattern: crm.objects.<object>.read or .write for records, crm.schemas.<object>.read or .write for property definitions, plus feature scopes such as automation for workflows. Pick by job:
| Job | Scopes to request |
|---|---|
| Read contacts | crm.objects.contacts.read |
| Update deals | crm.objects.deals.read, crm.objects.deals.write |
| Create contact properties | crm.schemas.contacts.write |
| Create deal properties | crm.schemas.deals.write |
| Create or edit workflows | automation, plus read scopes for the objects the workflow uses |
| Read or write sensitive properties | The matching .sensitive scopes, on top of the object scopes |
HubSpot’s API reference lists the accepted scopes for each endpoint, so check the endpoint page before guessing. See creating a property and creating a workflow for two common cases.
Common mistakes
- One key for everything. Use one credential per integration, so revoking one doesn’t break the rest.
- Write scopes “just in case.” A leaked token can do whatever its scopes allow.
- Forgetting the daily limit is shared. Every private app and service key in the account draws from the same allowance.
Where Jetstack AI fits
Jetstack AI’s own API uses the same principle with its own keys: each jsai_ key carries scopes (for example portals:read, hubspot:browse, hubspot:deploy), presets such as Read-only and Operator, and the two scopes that deploy Projects work or buy credits are never part of a preset. See authentication and scopes and the developer overview.
Sources
- Legacy private app creation sunset (HubSpot Developer Changelog)
- Legacy private apps overview (HubSpot Developers)
- Account service keys (HubSpot Developers)
- Create a property, 2026-03 (HubSpot API reference)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
API & developers
Do it from your own code or AI agent.
The Jetstack AI REST API, MCP server and CLI share API keys and scopes. Create and manage those keys in the app.
Read the developer docs