HTTP Node Issue w/ Go High Level

Describe the problem/error/question

Trying to fetch contacts in high level based on last name by using an HTTP node that is setup using header auth. The API i’m calling expects a valid JWT (JSON Web Token) in the request headers, but the token provided is missing, expired, or malformed. Not sure why as i’ve pasted the api key from the location settings in the high level sub-account with “Authorization” as the name and the value being “Bearer ”.

What is the error message (if any)?

Authorization failed - please check your credentials

Invalid JWT

Please share your workflow

Share the output returned by the last node

From HTTP Request
Error code
401
Full message
401 - “{"statusCode":401,"message":"Invalid JWT"}”
Request
{ “body”: { “query”: “Geddes”, “limit”: “20”, “locationId”: “7NU58m4inuzycZkzBZ3Z” }, “headers”: { “version”: “2021-07-28”, “Authorization”: “hidden”, “accept”: “application/json,text/html,application/xhtml+xml,application/xml,text/;q=0.9, image/;q=0.8, /;q=0.7” }, “method”: “POST”, “uri”: “https://services.leadconnectorhq.com/contacts/search”, “gzip”: true, “rejectUnauthorized”: true, “followRedirect”: true, “resolveWithFullResponse”: true, “followAllRedirects”: true, “timeout”: 300000, “encoding”: null, “json”: false, “useStream”: true }

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @cgeddz !
Why don’t you use HighLevel predefined credential type (API key / OAuth2).?

It handles the JWT .

However if you wanna stick with your Bearer to be sent trough header I think this is the proper way of using them directly :

As discussed here:

I suppose the type of credential you are usin is just sending a string … and not the JWT .
Cheers!