Home/HighLevel/Troubleshooting/API 401

Troubleshooting · Developers

Fix: GoHighLevel API 401 errors. Token, scope or account.

A 401 means the API did not accept your credentials. With private integration tokens that is usually an old token, a missing scope or the wrong account level.

  • 4likely causes
  • 5fix steps
  • 1escalation path
SymptomCausesFixConfirm
4
Likely causes4 to check1 ruled out
Diagnosis
Developers · SymptomAPI 401
Issue
1Old or rotated tokenRuled out
2Missing scopeChecking
3Wrong account levelTo check
4Header formatTo check
5 fix stepsToken, scope or account.Fix it, then confirm it works

The short answer

GoHighLevel API 401 errors usually mean the token is invalid or was rotated, it lacks the scope for that endpoint, it belongs to the wrong level (agency versus subaccount), or it is not sent correctly as a Bearer token in the Authorization header of the request.

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.

Causes

What causes HighLevel API 401 errors?

Most cases come down to the four causes in this table. Check each one before you change anything.

CauseHow to check
Old or rotated tokenPrivate Integrations list
Missing scopeToken scopes
Wrong account levelAgency vs subaccount token
Header formatAuthorization header in the request

Diagnose

How do you confirm what is causing the 401 before you change anything?

A 401 means the request was not accepted as authorized. The response usually says a little more, so read the full response body before you touch the token. Then make the smallest request you can: one that only reads data, such as fetching a contact, sent from a plain API client instead of your app. If that works, the token is fine and the problem is in how your code or tool sends it.

If the simple request also fails, open Settings, Private Integrations in the agency or the subaccount, wherever the token was made. Check that the integration still exists and look at the scopes selected on it. An agency token and a subaccount token are not interchangeable, so confirm which one you hold and which one the endpoint expects. The steps for a clean token are in create a private integration token.

A common story: a sync runs for months, then every call returns 401. Nobody changed the code. Someone rotated the token after a staff change, and the old value is still stored in the tool. Updating the stored token fixes it. If the job is simply moving data between apps, webhooks or Zapier may do it without custom code.

New to the API? Start with the GoHighLevel API overview.

Fix

Fix it step by step.

  1. Check the token in Private Integrations is active.
  2. Add the scope the endpoint needs, or create a new token.
  3. Use a subaccount token for subaccount endpoints.
  4. Send it in the Authorization header as a Bearer token.
  5. Retest with a simple read request.

Still stuck

When to contact support.

If none of these fix it, open Help and Support from the question mark at the top right of your agency view, then start a chat (AI Support Chat or Agent Chat), join a Zoom call or open a ticket. Have your Agency Relationship Number and the Location ID of the subaccount ready, add screenshots of the problem, and turn on Support Access so the team can look inside the account. Only Agency Admins and Agency Users can reach HighLevel support; subaccount users go through their agency.

  • One token per integration
  • Store tokens in a secrets manager

If it persists, send support the endpoint and method, the time of the request, the full error response, the name of the integration and whether it is an agency or subaccount token. Never send the token itself. Describe it by name.

For prevention, keep one token per integration with the fewest scopes it needs, store it in a password manager or secrets store, and write down what each one is for. When a person or tool no longer needs access, delete that token. If outbound automations fail at the same time, check fix a webhook not firing as well.

For a wider look at what the API can do, watch the video on the HighLevel workflow API and AI automations. If you want a clean account to test the fix in, the 30 day GoHighLevel trial through Michael's link gives you one. For an honest look at strengths and limits, read the HighLevel review.

Help & Support
Opens from the question mark at the top right of the agency view
Relationship Number0 000 000
1
Support AccessLets support look inside your account for a set time
3
Quick support actions
Start Chat
5
Before you contact supportHave these ready
1
Agency Relationship NumberTop of Help and Support, with a copy button
2
Location ID of the subaccountSettings, Business Profile, or the URL after /location/
3
Support Access turned onAgency Settings, Company, Advanced Settings. It expires on the date you pick
4
Screenshots and the exact errorWhat you did, what you expected, what happened
5
Pick a channelAI Support Chat, Agent Chat, a Zoom call, or a ticket by email
Agency Admins and Agency Users onlyBilling or login: +1 (888) 732 4197
Michael Reimer, Founder of CRM Pros
Michael's takeFounder of CRM Pros · HighLevel Commander

Never paste a token into chat or code to debug it. Rotate it if exposed.

Questions

Common questions.

Why is the HighLevel API returning 401?

HighLevel API 401 errors usually mean the token is invalid or was rotated, it lacks the scope for that endpoint, it belongs to the wrong level (agency versus subaccount), or it is not sent correctly as a Bearer token in the Authorization header of the request.

How do I prevent it?

Keep one token per integration with the fewest scopes it needs, store it in a password manager or secrets store, and write down what each one is for. When a person or tool no longer needs access, delete that token.

When should I contact HighLevel support?

Contact support once you have checked every cause on this page and it still fails, or when the fix sits on HighLevel's side. If it persists, send support the endpoint and method, the time of the request, the full error response, the name of the integration and whether it is an agency or subaccount token. Never send the token itself. Describe it by name.

What does a 401 error mean in the HighLevel API?

It means the request was not authorized. The token is missing, no longer active, sent in the wrong format, lacks the scope the endpoint needs, or belongs to the wrong account level.

Do I need a new token if a scope is missing?

Not always. Add the scope the endpoint needs to the integration in Settings, Private Integrations, or create a new token with the right scopes. Retest with a simple read request either way.

Should I use an agency token or a subaccount token?

Use a subaccount token for subaccount endpoints and for work on one client. It limits the damage if the token leaks. Keep agency tokens for agency level work.

Next step

See it in your own account. Thirty days, every feature.

Start a 30 day trial through Michael's link, 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
⌃

Site preview

Explore the next page

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