Skip to content
Book a build

Can you still create a HubSpot private app, and which scopes does it need?

No new HubSpot private app can be created any more: HubSpot disabled legacy private app creation on September 28, 2026 for new accounts and October 26, 2026 for existing ones. Existing private apps keep working. For new integrations in your own account, use a service key, which takes the same kind of object-specific scopes. Pick one read or write scope per object the integration touches, and nothing more.

On this page

What HubSpot supports natively

As of October 29, 2026:

Legacy private appService key
Create newNo (disabled September 28, 2026 for new accounts, October 26, 2026 for existing)Yes: Development → Keys → Service keys
Existing onesKeep working
ScopesObject-specific, edited on the Scopes tabObject-specific, editable after creation
What it can callREST APIsREST API requests only; no webhooks or UI extensions
Rate limitsPrivately distributed app limitsSame as privately distributed apps
Who can createSuper AdminSuper 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:

JobScopes to request
Read contactscrm.objects.contacts.read
Update dealscrm.objects.deals.read, crm.objects.deals.write
Create contact propertiescrm.schemas.contacts.write
Create deal propertiescrm.schemas.deals.write
Create or edit workflowsautomation, plus read scopes for the objects the workflow uses
Read or write sensitive propertiesThe 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

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

API & developers

Related questions.

Can you still create a HubSpot private app, and which scopes does it need?

No new HubSpot private app can be created any more: HubSpot disabled legacy private app creation on September 28, 2026 for new accounts and October 26, 2026 for existing ones. Existing private apps keep working. For new integrations in your own account, use a service key, which takes the same kind of object-specific scopes. Pick one read or write scope per object the integration touches, and nothing more.

Will my existing HubSpot private app stop working?

Not because of this change. HubSpot says all existing legacy private apps continue to work as they are. It recommends migrating them to the Developer Platform projects framework over time.

Can I add scopes to an existing private app?

Yes. You edit scopes on the app's Scopes tab and commit the change; the token string stays the same. Sensitive Data scopes can be added this way too, and take effect immediately.

How do I check which scopes a token has?

For a legacy private app token, POST to /oauth/v2/private-apps/get/access-token-info. It returns the token's scopes and the account's Hub ID.