My custom app is getting a 403 Forbidden when calling GET /api/v2/routing/queues. I’m using a service account with the routing:queue scope, which the docs say is sufficient for read access.
HTTP/1.1 403 Forbidden
Content-Type: application/json
{"errorMessage":"Access denied. Required scope: routing:queue:read"}
The error implies a specific sub-scope is needed, but routing:queue:read isn’t listed in the standard scope reference. Am I missing something here?