Getting a 403 Forbidden when hitting /api/v2/routing/queues via our internal dashboard script. The token is fresh, generated using client credentials, and works fine for reading user profiles. Here’s the cURL command I’m running:
curl -X GET https://api.mypurecloud.com/api/v2/routing/queues
-H “Authorization: Bearer ”
The response is just {"error": "Forbidden"}. I’ve added routing:queue:view and routing:queue:member:view to the client scopes in the Admin UI, but it still fails. Is there a specific scope I’m missing for this endpoint?