Im using OAUTH2 with the HighLevel Lead Connector
Your UI says, “You don’t have to add authorization headers; we already did that for you.”
but thats not true because on error i can see no Authorization Headers were added, nor was the Bearer Token. Therefore my requests produce 404 errors because the API call is never Authorized.
Because You Handle OAUTH2 in the browser I am unable to get the access token sent in the redirect_uri
Im trying to make a generic API call to update custom values in a HighLevel Lead Connectior account
Here is the documentation for the specific task Im trying to accomplish: Update Custom Value | Integrations API
Here is the Get Access token API that is having errors on Make:
in this first image im confused because i think i have it all in correct so i can get the access token i need as the bearer token for my authorization header in my next call - but as you can see and when compared to GHL docs it does fail:
you can see here in this image how it says that authorization headers dont need to be added because Make will add them but i dont see those headers in the error and since im getting a 404 NOT AUTHORIZED error im thinking Make has a bug here in their OAUTH2 implementation that needs to be fixed so that i can add headers or they do it…
could be my payload is wrong but i doubt it because in the docs here: https://www.make.com/en/help/tools/http#make-an-oauth-2-0-request you can find where it says that the redirect uri has to be: https://www.integromat.com/oauth/cb/oauth2
that was wrong and it ended up being https://www.make.com/oauth/cb/oauth2
you can see here where ive even inuluded the Version attribute as required by the GHL docs also in this doc: Get Custom Values | Integrations API and what im missing is the ability to add the bearer token.
anybody get oauth2 working for ghl yet???
