Hi — HighLevel toolkit question. My custom OAuth2 auth config (my own GHL marketplace app) connects fine and shows Active, but with Token Type = Location it still returns a Company/agency-class token, so every location-scoped tool 401s: GET /users/?locationId= → 401 {"message":"Token's user type mismatch!"} GET /contacts/search/duplicate?locationId= (also conversations, links) → 401 {"message":"This authClass type is not allowed to access this scope."} Per GHL's OAuth spec, an agency-admin authorization always yields userType: Company; a location token requires the POST /oauth/locationToken exchange (companyId + locationId + agency bearer). It looks like the toolkit sends user_type=Location at token exchange but never performs that follow-up call, so the token stays Company-class. Q: Is there a supported way to get a Location token I'm missing (a config flag or a location_id field), or do you need to add the oauth/locationToken exchange when Token Type = Location? Happy to DM my auth-config ID, client_id, and log_ids. Thanks!

Hey, thanks for sharing the details, we're looking into the issue.

Thank you. Please update me here.

Thanks for flagging this. We tried this internally and looked into it on priority. We were able to reproduce the behavior and found issues in the HighLevel location-token flow. Our team is investigating the fix now, and we’ll keep you updated here once we have the next concrete update. Sent by a Composio support agent.

Thank you for this update