Short answer
A 400 error means GoHighLevel received your request but could not accept it. The request itself is wrong, not the server. In GoHighLevel this happens when another tool talks to GHL through the API, for example Zapier, n8n, Make, or a WordPress form sending leads to the CRM. In a live test on 9 Nov 2026, a filter on an unknown field name returned 400 with a message naming the field, so read the full error message first. Check the Version header early too: every v2 call must carry Version: 2021-07-28, and a missing header breaks the call. A missing header returns 401, not 400, as the test below shows.
In this post
- What a 400 error means
- Where it shows up in GoHighLevel
- 401, 400 and 422 compared (tested 9 Nov 2026)
- A missing Version header returns 401, not 400
- The 6 causes, ordered by how well each is supported
- How to fix it, step by step
- When it is not your bug
- FAQ
- Sources
What a 400 error means
400 is the HTTP status code for Bad Request. The server understood that a request arrived, but the request was malformed, incomplete, or invalid, so the server refused it. It is different from the errors people confuse it with:
- 401 means authentication failed. In a test with a valid token, a missing Version header also returned 401 with the message ‘version header was not found’.
- 403 means the token is valid but lacks the scope the endpoint needs, or belongs to a different location. That is a permission problem.
- 422 is the code many APIs return when a field value is rejected after validation. Check the response body to see which field it names.
- 400 means the request itself is bad. Fix the request, not the token.
Where it shows up in GoHighLevel
A 400 shows up where GoHighLevel meets another system:
- Zapier, n8n, or Make workflows that create contacts, update opportunities, or change appointment status through the API.
- WordPress forms or funnels that send submissions into GHL.
- OAuth authorisation, when connecting an app such as n8n to a GHL location.
- Any custom integration calling
services.leadconnectorhq.com.
If the error appears in one of those tools, the fix is in the request that tool sends, not in a GHL setting.
401, 400 and 422 compared
All three results below come from live API tests run on 9 Nov 2026. Each names the endpoint it was tested on.
- 401: a valid Private Integration token with no
Versionheader, sent to GEThttps://services.leadconnectorhq.com/locations/{locationId}, returned 401 with the body{"statusCode":401,"message":"version header was not found."}. The same call withVersion: 2021-07-28returned 200. So a missing Version header is an authentication failure, not a bad request. - 400: a filter on the field
date_added(snake_case), sent to POSThttps://services.leadconnectorhq.com/contacts/search, returned 400 with the body{"message":"Invalid field date_added","error":"Bad Request","statusCode":400}. The operation reference says field names use camelCase and snake_case is rejected. This is the tested 400 this post leads with. - 422: a filter operator
equals, which is not in the allowed list, sent to the same endpoint, returned 422 with a message listing the allowed values (eq,not_eq,contains, and others). The message names what is allowed, so read it before changing the request.
The 400 vs 422 distinction is what the tests showed on one endpoint, not a rule for all endpoints. On other endpoints the line between them may differ, so always read the message the endpoint returns.
A missing Version header returns 401, not 400
Every GoHighLevel API v2 call must carry the header Version: 2021-07-28, alongside Authorization: Bearer <token>. The HighLevel API reference lists Version as a required header with the single allowed value 2021-07-28. A missing header breaks the call, but it does not return a 400. Tested on 9 Nov 2026: a valid Private Integration token with no Version header, sent to GET https://services.leadconnectorhq.com/locations/{locationId}, returned 401 with the message version header was not found. The same call with the header returned 200. This was tested on one GET endpoint with a Private Integration token; it was not tested on POST, PUT or other endpoints.
So keep the Version header as the first thing to check for any 401 or 400 on v2, because the test proves a missing header breaks calls. But if the error is a 400, the header is not the cause. Work through the causes below instead.
The 6 causes, ordered by how well each is supported
1. A field name or value the endpoint does not accept (tested)
Tested on POST /contacts/search, 9 Nov 2026: a filter on the field date_added returned 400 with the message Invalid field date_added. The operation reference says field names use camelCase and snake_case is rejected. A wrong field name is the one 400 cause confirmed by a live test, so check it first.
Fix: read the error body in full. It usually names the field. Then check that field against the API reference for that endpoint, not against a tutorial.
2. A required field is missing or wrong
Required and allowed body fields differ by endpoint. The Update Appointment reference lists no locationId in the body, so check the reference for your endpoint instead of copying forum advice.
Fix: open the reference for the endpoint you are calling and check the required fields it lists. Send only the fields it lists, with the names and shapes it shows.
3. Wrong HTTP method or endpoint
A POST sent to an endpoint that expects a PUT, or a v1 path used with a v2 call. The appointment status case is the clearest example: the old v1 path used POST to rest.gohighlevel.com/v1/appointments/{id}/status, while v2 uses a PUT to services.leadconnectorhq.com/calendars/events/appointments/{eventId} with the status in the body. The status goes in the appointmentStatus field, which takes new, confirmed, cancelled, showed, noshow, invalid, completed or active.
Fix: check the method and the full path in the current API reference. Test the exact call in Postman or with a plain curl call before blaming the automation tool.
4. A malformed request body
The body is not valid JSON, a field is the wrong shape, or a value is in the wrong format. The tests above show the boundary on one endpoint: an unknown field name returned 400, while an operator outside the allowed list returned 422. Both point at the body, and the error message tells you which one you have.
Fix: send the smallest valid body first, then add fields back one at a time until it breaks. That finds the bad field faster than re-reading the whole payload.
5. Calling the old v1 API (unconfirmed)
The old endpoint rest.gohighlevel.com/v1 reached end of support on 31 December 2025. Tutorials that still show it are out of date. The sources checked do not say which error a v1 call returns, so replace any v1 URL first, whatever error you see. Move to v2 at https://services.leadconnectorhq.com.
Fix: change the base URL to https://services.leadconnectorhq.com, send the Version header (see the 401 section above), and check the v2 endpoint name.
6. OAuth scope formatting during connection (unconfirmed)
When connecting an app such as n8n to GHL, the scopes are typed as a space-separated list. In one n8n thread, a HighLevel developer found two spaces between scopes and another user fixed the same error by retyping them. The original poster still could not connect, so rule this out, but do not expect it to be the fix. Copying and pasting the list is what introduces the extra spaces.
Fix: delete the scopes and type them again by hand, with single spaces. Then retry the connection before changing anything else.
How to fix it, step by step
Work in this order. Stop at the first step that fixes it.
- Read the full error response, not just the number. Copy the message and the trace ID if there is one. The message usually names the field.
- Check the Version header. It must be present on v2 calls, with the value the docs list for that endpoint (
2021-07-28on the endpoints tested here). - Check the base URL and version. It should be
https://services.leadconnectorhq.com, notrest.gohighlevel.com/v1. - Check the required fields in the reference for that endpoint.
- Test the same call in Postman or with a plain curl call using the same token. If it works there, the problem is in the automation tool’s setup, not in GHL.
- If it still fails, simplify the body to the minimum required fields and add fields back one at a time.
When it is not your bug
A 400 is, by definition, a problem with the request, so it is almost always fixable on your side. Two exceptions: the endpoint itself is down or returning bad responses for everyone, which shows up as 5xx errors rather than 400s; and a GHL-side change to an endpoint, which the changelog will show. If the same request worked yesterday, stopped today, and nothing changed on your side, check the GHL changelog and status page before rebuilding the integration.
If you have worked through the steps above and the error message still makes no sense, open a support ticket with the full request (headers with the token removed), the full error body, and the trace ID. That is what support needs to help.
FAQ
What does a 400 error mean in GoHighLevel?
It means GHL received the request but rejected it as invalid. The request is wrong, not the server. It most often comes from an API or integration call.
What should I check first?
Read the full error message first. In a test on 9 Nov 2026, an unknown field name returned 400 with a message naming the field. Then check the Version header: a missing header breaks v2 calls, and the test showed it returns 401, not 400.
Is a 400 error the same as a 401 or 403?
No. 401 means authentication failed. A missing Version header also returns 401 (tested 9 Nov 2026). 403 means the token lacks the scope or location. 400 means the request itself is bad. They need different fixes.
Why does my Zapier or n8n workflow get a 400 from GoHighLevel?
The request the tool sends uses the retired v1 endpoint, is missing a required field, or uses a field name the endpoint does not accept. Read the error body in the failed step: it usually names the problem.
Can a 400 error come from a form submission?
Yes, when a form sends data to GHL through an integration or webhook. Check the integration’s request first: header, endpoint, required fields, and body shape.
Should I just retry the request?
No. Retrying the same bad request returns the same 400. A retry only helps after you change something, and only for temporary errors such as 429 or 5xx.
What this post does not cover
This post covers the 400 errors practitioners actually hit when connecting tools to GoHighLevel. There is no HighLevel Help Center article on the 400 error. The 401, 400 and 422 results above come from live API tests run on 9 Nov 2026 on the endpoints named. The other causes come from HighLevel’s API examples and versioning docs, practitioner guides and forum threads, checked 2026-11-09, and the unconfirmed ones are labelled as such. If you see a 400 inside the GHL app with no integration involved, note the exact screen and message and check with support, because that case is not covered here.
Need this fixed in your account?
If an integration keeps failing with 400 errors and you would rather have it fixed than debug it, book a free 30-minute call. The Audit (founding price $97) checks your domain, email, phone, A2P, calendars and workflows, and ends with a fix list.
Sources
Checked 2026-11-09. All GHL behaviour in this post comes from these sources, not from memory.
- HighLevel Marketplace API reference, Update Appointment: lists
Versionas a required header with the single allowed value 2021-07-28, andappointmentStatusas the status field (new, confirmed, cancelled, showed, noshow, invalid, completed, active). https://marketplace.gohighlevel.com/docs/2021-07-28/ghl/calendars/edit-appointment.md - Live API tests run 9 Nov 2026. 401 for a missing Version header (GET /locations/{locationId}): sent with curl from a terminal, using a Private Integration token. 400 for an unknown field name and 422 for an operator outside the allowed list (both POST /contacts/search): sent through the GHL connector. Exact trace IDs not published.
- HighLevel Support Portal, Private Integrations: official examples show the
Version: 2021-07-28header on v2 calls. https://help.gohighlevel.com/support/solutions/articles/155000003054-private-integrations-everything-you-need-to-know - GoHighLevel API v2 Guide (Yousaf Dev): the Version header is mandatory on v2 calls; forgetting it returns an error that reads like an authentication problem. https://www.yousafdev.com/blog/gohighlevel-api-v2-guide
- n8n Community, “Cannot connect n8n to HighLevel V2 API, getting 400 error”: scope spacing was reported as a cause; not confirmed by the original poster. https://community.n8n.io/t/cannot-connect-n8n-to-highlevel-v2-api-getting-400-error-help/66566
- Latenode Community, “Zapier webhook returns 400 bad request when changing appointment status in GoHighLevel”: v1 endpoint deprecated. Forum answers say v2 expects PUT with locationId in the body, but the official Update Appointment reference lists no locationId. https://community.latenode.com/t/zapier-webhook-returns-400-bad-request-when-changing-appointment-status-in-gohighlevel/22459
- WordPress GoHighLevel Integration: Webhook vs API v2 (WPWebhooks): v1 API keys reached end of support on 31 December 2025; v2 base URL is services.leadconnectorhq.com. https://wpwebhooks.org/blog/wordpress-gohighlevel-integration/



