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

Hit a weird wall trying to list queues via the JS SDK. The token has admin:queue and routing:queue, but the call to routingApi.getQueues() keeps returning 403. Checked the event logs and the payload looks fine, just getting blocked at the auth layer. What scope am I missing?

The docs for GET /api/v2/routing/queues state: “Requires one of the following scopes: routing:queue, routing:queue:read”. Your admin:queue scope is for write operations. Switch to routing:queue:read. It’s a common mix-up.

// Use this scope in your token request
'scope': 'routing:queue:read'