Is it possible to resolve 403 on /api/v2/routing/queues despite having routing:queue view scope?

NICE CXone API & Integrations
1

Is it possible to resolve a persistent 403 Forbidden error when attempting to fetch queue details via the REST API, even though the service account possesses the routing:queue:view scope? I am building a real-time dashboard that requires frequent polling of queue metrics, and I have verified the OAuth token is valid and active. The documentation explicitly states, “The routing:queue:view scope allows read-only access to queue configuration and statistics.” However, my Node.js client receives a 403 response with the body: {"code":"forbidden","message":"You do not have permission to perform this operation"}.

I have already tried the following:

  • Confirmed the service account is a member of the necessary organization roles and that the routing:queue:view scope is explicitly included in the token response.
  • Attempted to use the Platform SDK’s apiClient.setAccessToken method to ensure the token is correctly bound to the request context before calling QueuesApi.getRoutingQueue(id).

The endpoint /api/v2/routing/queues/{queueId} returns 403, yet the same token works for /api/v2/users/me. Is there a secondary permission or a specific tenant-level setting that overrides the OAuth scope for routing resources?