403 Forbidden on GET /api/v2/routing/queues despite admin role

Getting a 403 when hitting GET /api/v2//queues. The token has admin:users:view but that’s not enough. Which exact OAuth scope is required for queue read access? Trying to build a custom dashboard and the API keeps rejecting the call.

The token you’re using probably only has admin:users:view, which is way too narrow for queue data. You need :queue:view to actually read queue details. Without that specific scope, the API will always throw a 403, even if your user account is a super admin.

Here’s how to check and fix your token scopes in the developer portal:

  1. Go to your app settings in the Genesys Cloud developer portal.
  2. Under OAuth 2.0, add :queue:view to the required scopes.
  3. Re-authorize your app to get a new access token.

You can test if it’s working with a quick curl command:

curl -X GET "https://api.mypurecloud.com/api/v2//queues" \
 -H "Authorization: Bearer YOUR_NEW_TOKEN"

If you still get a 403, double-check that the user associated with the token actually has the “Queue” permission set in their role. Sometimes the role doesn’t have the right capabilities enabled, which blocks the API call regardless of the token scopes.