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
- Identify which third party tools or automations are using the legacy API key.
- Make a list of these tools and note what each does.
- Log into HighLevel.
- Open Settings and locate Private Integrations.
- Click Create Private Integration.
- Enter a descriptive name and optional description.
- Select only the scopes the tool requires.
- Click Save to generate a Private Integration Token.
- CRITICAL: Copy and store the token securely; it will be shown only once.
- Do NOT update or edit any existing active automations at this stage.
- Open the external automation platform.
- Create a brand new automation (or duplicate the existing one for backup).
- Connect HighLevel using the copied token.
- Add the Authorization header as Bearer <YOUR_NEW_TOKEN> if required.
- Build the automation steps using the current API endpoints.
- Run a test lead or action through the new workflow.
- Verify the data appears correctly in HighLevel and that scopes are sufficient.
- Activate the new automation.
- Pause or turn off the old automation that uses the legacy key.
- 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
- Select the API version to use in your requests API version guide
- Set up webhooks for your app using HighLevel OAuth V2 Webhook setup
- View pricing and plan details for API endpoint access Pricing and plans
Michael's take

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