Home/HighLevel/Features/Developer Resources/HighLevel private integration token migration: full guide

Agency, Settings and Integrations

HighLevel private integration token migration: full guide

In short

Private Integration Tokens replace old API keys with scoped, secure access for each external tool. They let you select exact permissions, generate a one time token, and protect your account while you create and test new automations before retiring the legacy API.

AreaDeveloper Resources · Developer Resources
Used forMarketing agency, Health clinic, SaaS startup
PlanAll plans (some endpoints require Founder Plan)
Setup steps20 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders who rely on Zapier or Make for lead capture can limit token access to only contacts.
  • Marketing agencies managing multiple client subaccounts can create separate tokens for each client integration.
  • Product teams building custom web forms can grant only the required data permissions through a private token.

02Private Integrations, explained

A Private Integration Token is a secure credential that grants an external tool only the permissions you select. Unlike the old API keys, it does not give blanket access to all account data.

Tokens are created in the Settings area of HighLevel at either the agency level or a subaccount level. When you save a token you choose specific scopes such as Contacts, Opportunities, or Appointments, and HighLevel generates a single use token.

The token is shown only once, must be copied immediately, and is used in the Authorization header as Bearer followed by the token value. It works with the current API endpoints and respects the version header defined in the documentation.

03How businesses use Private Integrations

  • Marketing agency. The agency creates a private token for each client’s Zapier integration, selecting only the Contacts scope. Zapier then uses the token to pull new leads without exposing other client data.
  • Health clinic. The clinic builds a new automation in Make that writes appointment data to HighLevel. It authenticates with a private token that includes the Appointments scope, ensuring the integration can only modify schedules.
  • SaaS startup. The startup replaces its custom webhook calls with a private token that grants access to the Users scope. The webhook sends the Authorization header with the token to create new user records.

04The numbers and rules that matter

  • HighLevel API v1 end of support on December 31, 2025.
  • Rotate tokens every 90 days for maximum security.
  • Grace period of 7 days when rotating tokens.
  • Current APIs use the Version request header and may use named versions such as v3.

05Before you start

  • Do not edit or update any existing active automations before the migration is complete.
  • Confirm that any API endpoints you will use are allowed on your current plan; some require a Founder Plan.

06How to set up and use Private Integrations in HighLevel

Migrate to Private Integrations

  1. Identify which third party tools or automations are using the legacy API key.
  2. Make a list of these tools and note what each does.
  3. Log into HighLevel.
  4. Open Settings and locate Private Integrations.
  5. Click Create Private Integration.
  6. Enter a descriptive name and optional description.
  7. Select only the scopes the tool requires.
  8. Click Save to generate a Private Integration Token.
  9. CRITICAL: Copy and store the token securely; it will be shown only once.
  10. Do NOT update or edit any existing active automations at this stage.
  11. Open the external automation platform.
  12. Create a brand new automation (or duplicate the existing one for backup).
  13. Connect HighLevel using the copied token.
  14. Add the Authorization header as Bearer <YOUR_NEW_TOKEN> if required.
  15. Build the automation steps using the current API endpoints.
  16. Run a test lead or action through the new workflow.
  17. Verify the data appears correctly in HighLevel and that scopes are sufficient.
  18. Activate the new automation.
  19. Pause or turn off the old automation that uses the legacy key.
  20. Delete the old legacy API key from HighLevel settings and from the external tool.

07Settings that matter

  • Scopes. Controls which permissions the private token grants, allowing you to limit access to specific data types such as contacts or appointments.

08Things to know before you rely on it

  • Private Integration Tokens are available on all plans, but certain API endpoints require Founder Plan access.
  • The token is displayed only once; you cannot view it again after saving.
  • HighLevel API v1 reached end of support on December 31, 2025.
  • Rotate your tokens every 90 days; both old and new tokens remain active for a 7 day grace period during rotation.
  • Do not modify existing active automations until the new automations are verified.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Private Integrations let you replace legacy API keys with scoped tokens.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about Private Integrations.

What is a Private Integration Token?

It is a credential that grants an external tool only the permissions you select, replacing the broad access of legacy API keys.

Why can’t I keep using my old API key?

Support for API version 1 ended on December 31, 2025, and legacy keys are no longer maintained or supported.

Do I need a Founder Plan to use Private Integration Tokens?

Tokens are available on all plans, but some API endpoints that you may need require Founder Plan access.

How often should I rotate my token?

HighLevel recommends generating a new token every 90 days. During rotation both tokens stay active for a 7 day period.

Can I use the same token for multiple tools?

Create a separate Private Integration for each tool. Sharing one token across multiple tools is not recommended.

Where can I see the token after I create it?

The token is shown only once when you save the Private Integration. You must copy it immediately because it cannot be viewed again.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.