Fix: GoHighLevel API v1 deprecated — migrate to v2
HighLevel ended API v1 on 26 June 2026: no patches, no support, no new keys. Here's how to find what still uses it and move each integration to Private Integrations or OAuth.
Symptoms — what you're seeing
- You got an email or banner saying "HighLevel API v1 is deprecated" and don't know which integration triggered it
- The option to generate a new v1 API key is gone from your sub-account settings
- An old Zap, Make scenario, n8n workflow or custom script still uses a "Location API Key"
- HighLevel support says they can't troubleshoot a v1 integration
Why this happens
HighLevel announced the end of life of API v1 on 26 June 2026. There's no hard shut-off date yet, and v1 integrations keep running for now. But v1 no longer gets security patches, bug fixes or new features, support won't troubleshoot it, and you can't create new v1 keys. In practice, the next v1 outage is yours to fix with no help, at whatever moment it happens.
The v1 "API key" was a single unscoped key per location that unlocked everything. v2 replaces it with Private Integration tokens for your own tools and OAuth 2.0 for apps installed across many accounts. Both are scoped: each token can only do what you granted. The base URL, required headers and many endpoint shapes changed as well, so this is a migration, not a key swap.
One thing that does not need migrating: webhooks built inside GHL workflows (the Webhook / Custom Webhook action) and inbound webhook triggers. They aren't calls to the v1 API, so they keep working as they are.
The fix, step by step
- Find everything still on v1. Search every codebase, n8n instance and scenario for the old host and key:
grep -rn "rest.gohighlevel.com" . # n8n: export workflows and search the JSON n8n export:workflow --all --output=all.json && grep -o "rest.gohighlevel.com[^\"]*" all.json | sort -u
Then check Zapier and Make for connections created with an API key rather than an OAuth login. List each one with its owner and the client it serves. - Pick the credential type. For your own automations in a sub-account, use a Private Integration (Settings → Private Integrations). If you ship an app installed across many agencies or locations, use OAuth 2.0 through the HighLevel Marketplace. Grant only the scopes each integration uses.
- Change the request basics. Every v2 call needs a new host, a Bearer token and a
Versionheader. Most also need thelocationIdsent explicitly, because the v1 key implied it:# v1 GET https://rest.gohighlevel.com/v1/contacts/?query=jane@acme.com Authorization: Bearer <location_api_key> # v2 GET https://services.leadconnectorhq.com/contacts/?locationId=<locationId>&query=jane@acme.com Authorization: Bearer pit-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Version: 2021-07-28
- Map the endpoints you actually use. Most agency integrations touch a handful:
Response shapes and pagination differ too, so re-map every field your downstream steps read. Don't assume the JSON looks the same.What it does v1 v2 Create / update contact POST /v1/contacts/POST /contacts/upsertFind contact GET /v1/contacts/lookupGET /contacts/?query=orPOST /contacts/searchTags POST /v1/contacts/:id/tags/POST /contacts/:id/tagsOpportunities /v1/pipelines/:id/opportunities/POST /opportunities/(pipelineId in body)Book appointment POST /v1/appointments/POST /calendars/events/appointments - Migrate one integration at a time. Build the v2 version next to the v1 one, run both against a test sub-account, compare the results, then switch. Moving everything at once means one bad field mapping breaks every client together.
- Retire the v1 key. Once nothing calls v1, check that the deprecation notice stops, and remove the old key from every credential store so nobody wires it back in.
Common variations
- "I got the email but I don't use the API" — something you connected does. Usually it's an old Zap or Make connection, or a third-party tool set up with your API key years ago. Reconnect those apps through their current HighLevel/LeadConnector integration, which uses OAuth.
- "My v2 calls return 401" — missing
Versionheader, a v2 token sent to the v1 host, or a doubledBearer. See n8n 401 unauthorized on the GHL API. - "My v2 calls return 403 'does not have access to this location'" — the token was created in a different sub-account than the
locationId. See GHL token does not have access to this location. - "Do my GHL workflow webhooks need migrating?" — no. Outbound Webhook actions and inbound webhook triggers aren't v1 API calls.
- "Can I still create a v1 key for a new client?" — no, generation is disabled. New integrations have to start on v2.
When this isn't the issue
- If v2 calls work but fail in bursts with 429, you're hitting rate limits — see the GHL API rate-limit strategy.
- If you're moving n8n workflows off the native HighLevel node at the same time, see n8n HighLevel node not working.
Got a stack of v1 integrations across client sub-accounts? This is exactly the kind of migration I take on — send me the list and I'll tell you what breaks first.
Need this workflow customized or debugged? Book a 30-min scope call →
Stuck configuring this workflow?
I build and fix n8n workflows for agencies and SaaS teams. 30-minute scope call — bring the problem, leave with an estimate.