403 Forbidden on /api/v2/routing/queues despite admin scope?

Hey folks,

Running into a weird auth issue with the Genesys Cloud REST API. I’m trying to fetch a list of routing queues using GET /api/v2/routing/queues, but I keep hitting a 403 Forbidden error.

Here’s the setup:

  • I’m using a Service Account (not a user account).
  • The account has the admin role assigned in the UI.
  • I’ve granted the routing:queue scope (and even tried routing:queue:view just in case).
  • The OAuth token looks valid (decoded it, expires in an hour).

I can successfully call GET /api/v2/users/me with the same token, so the auth header isn’t the problem. It’s specifically the routing endpoint that’s blocking me.

Is there a hidden scope I’m missing? Or is the Service Account role not actually granting the underlying permissions it claims to? I’ve checked the scope documentation and routing:queue seems to be the one.

Here’s the curl command I’m using for testing:

curl -X GET "https://myorg.mygen.com/api/v2/routing/queues" \
 -H "Authorization: Bearer <TOKEN>" \
 -H "Content-Type: application/json"

Returns 403 Forbidden. Any ideas what’s tripping this up?