Hi team,
we’re facing the issues when developing custom pieces to call the GHL API V2…
Creating a new Auth using PieceAuth.OAuth2
Creating a new Piece with Auth (in num 1)
When try to Call API - it returning this kind of value
{
"response": {
"status": 401,
"body": {
"message": "E-102. This AuthClass is not yet supported!",
"error": "Unauthorized",
"statusCode": 401
}
},
"request": {}
}
Even trying the built-in node HighLevel V2, returning same results
How should we do with this?
Thanks for the help
Hi @Antonio_Monteiro , Welcome to the community ,
What parameters are used for the ‘Search Users’ endpoint, such as companyId
and locationId
? Both of these will be included in the response from the access token endpoint .
Hi Hi,
We’re already try to use as documented here:
Query params:
query from props
companyId from context.auth
Headers
Authorization: 'Bearer '+token from context
Version: '2021-07-28'
scope -> user.readonly
But returning that 401 error
Hopefully we can get solution for this
Thanks
Please try including both locationId
and companyId
and see if that resolves the error.
Hey it works, thanks a lot.
But why it needed, in the docs only companyId required
And also, why the built-in node didn’t work when we try to call in Custom API Call??
Did you include both locationID
and companyID
when using the custom API call? Also, are you using your own GHL OAuth2 app or one from AP?
Q1: Did you include both locationID and companyID when using the custom API call
Actually no, because i’m thinking after we connect the account, let’s say the sub-account
… I’m expecting it will automatically appended to the params, no need to add more, since it was already retrieve the credentials …
Q2: using your own GHL OAuth2 app or one from AP
we try both
system
Closed
August 2, 2024, 2:46pm
8
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.