Quick query here. I’m trying to fetch queue details for a hybrid dashboard integration, but I keep hitting a wall with authentication.
I’ve got a valid OAuth token generated via the client credentials flow. The token itself looks fine, and I can successfully call other endpoints like /api/v2/users/me to verify the identity. However, when I hit the queues endpoint, the server immediately rejects the request.
Here’s the curl command I’m running:
curl -X GET "https://api.mypurecloud.com/api/v2/routing/queues" \
-H "Authorization: Bearer <valid_token>" \
-H "Accept: application/json"
The response is a straight 403 Forbidden. No helpful error body, just the status code. I’ve checked the app permissions in the Genesys Cloud admin portal. I’ve added routing:queue, routing:queue:read, and even routing:queue:write to the app’s OAuth scopes. I’ve revoked and re-issued the token multiple times to ensure the new scopes are active. Still getting the 403.
I’m using an org admin user for the client credentials flow, so role-based access control shouldn’t be the issue here. The user definitely has the necessary roles to view queues. It feels like the scope name is slightly off or there’s a specific prefix I’m missing.
Is there a particular scope string that’s required for this endpoint that isn’t obvious from the docs? Or is there a secondary permission check happening at the org level? I’ve tried clearing the cache and waiting an hour for pagation, no change. Just want to get this basic read working before I move on to the more complex routing logic. Stuck on this auth step.