Home/HighLevel/How to/Private integration token
How to · API
How to create a private integration token in GoHighLevel. Secure API access with only the scopes you need.
A private integration token (PIT) gives a tool or developer API access to one GoHighLevel agency or subaccount, limited to the permissions you choose. It is how you connect custom apps, scripts and AI agents to HighLevel.
Secure API access with only the scopes you need.
The short answer
To create a private integration token in GoHighLevel, open Settings, Private Integrations in the agency or subaccount, click Create new Integration, give it a name and description, select only the scopes it needs, then copy the token and store it in a password manager or secrets store.
Michael is a sponsored HighLevel affiliate. Links to HighLevel use his partner link at no extra cost to you. HighLevel prices and product facts on this page come from HighLevel's own pricing page and help center, checked on the date above.
Create
How do you create a private integration token in HighLevel?
- Open Settings, then Private Integrations, in the agency or the subaccount.
- Click Create new Integration.
- Name it and describe what it is for.
- Select only the scopes the integration needs.
- Copy the token and store it in a password manager or secrets store.
- Share it only with the trusted developer or tool that needs it.
Security
Keep it safe.
- Never paste a token into public code, chats or documents
- One token per integration, so you can revoke one without breaking others
- Use the fewest scopes possible
- Rotate or delete the token immediately if it is exposed
- Delete tokens you no longer use
Before you start
What do you need before you create a private integration token?
A token is a key, so decide who gets it before you make it. In HighLevel, or GoHighLevel as API guides often write, settle these first.
- Admin access to the agency or subaccount
- The exact list of what the tool needs to read or change
- A decision between an agency token and a subaccount token
- A password manager or secrets store to keep it in
- The name of the tool or developer it is for
For the bigger picture, read what the GoHighLevel API does and which plans include it.
Test it
How do you test a private integration token?
Test with the least risky request you can make.
- Pass the token to the tool or developer through a secure channel.
- Run one request that only reads data, such as fetching a contact.
- Confirm it succeeds.
- Try an action the token has no scope for and confirm it is refused.
- Record what the token is for and when it was created.
Common mistakes
What mistakes should you avoid when you create a private integration token?
- Selecting every scope. Choose only the scopes the integration needs.
- One token for everything. Use one token per integration so you can revoke one without breaking the others.
- Pasting it into a chat or document. Store it in a password manager or secrets store only.
- Using an agency token for one client. A subaccount token limits the damage if it leaks.
- Leaving old tokens alive. Delete tokens you no longer use. If requests fail, see fix API 401 errors.

Treat a token like a key to the business. Because it is one.
Questions
Common questions.
What is a Private Integration Token in GoHighLevel?
A Private Integration Token, or PIT, gives a tool or developer API access to one HighLevel agency or subaccount, limited to the scopes you choose. It is how you connect custom apps, scripts and AI agents to the account. You create it under Settings, Private Integrations and store it like a password.
How many can I create?
HighLevel currently allows up to 20 tokens per subaccount. The limit can change, so check the Private Integrations page in your own account. Use one token per integration instead of sharing one across tools. That way you can revoke a single token without breaking the others, and you can delete tokens you no longer use.
What if a token is leaked?
Rotate or delete it right away and create a new one. A leaked token gives API access with whatever scopes you selected, so treat it like an exposed password. This is why one token per integration and the fewest scopes possible matter. Never paste a token into public code, chats or documents.
Agency or subaccount token?
Use a subaccount token when the integration only needs one business. A subaccount token limits the damage if it leaks, because it reaches a single account. Use an agency token only when the tool has to work across the agency. Decide which one you need before you click Create new Integration.
What is a private integration token used for?
Connecting custom apps, scripts and AI agents to one HighLevel agency or subaccount through the API, with only the permissions you choose. Check the HighLevel integrations page for a ready made option first. If custom connections are a deciding factor for you, read is HighLevel worth it before you pick a plan.
What should I do before sharing a token with a developer?
Limit it to the scopes they need, name it after the project and send it through a secure channel. Ask them to run one request that only reads data first. Record what the token is for and when it was created, then delete it when the work is finished.
Can AI assistants use a token?
Yes. HighLevel's MCP server lets AI assistants work with your account through a token like this. See Claude and MCP with HighLevel. Give the assistant its own token with the fewest scopes possible. You can test this inside a 30 day GoHighLevel trial through Michael's link before you commit to a plan.
Keep reading
Related pages.
Next step
See it in your own account. Thirty days, every feature.
Start a trial, build the first system and test it before the first invoice. Usage fees for phone, SMS, email and AI can apply during the trial.
HighLevel has three plans at a flat monthly price, each with unlimited users and contacts. See what each one includes and what it costs.
Compare the PlansStarter, Unlimited and Founder