Missing or invalid Bearer token. Note that in practice, requests made without a valid token may receive a 302 redirect response at the gateway level rather than a 401 JSON error. Ensure your HTTP client does not automatically follow redirects when an unexpected 302 is received — this is an indicator of a missing or expired token.
404
Returned when a timeout occurs waiting for initial metrics. Note that providing an unrecognized or non-existent queueId does not return a 404 — the API returns a 200 with all metrics fields zeroed out in that case.
500
Internal server error.
503
Service temporarily unavailable. Retry after a short delay.
Click Try It! to start a request and see the response here! Or choose an example:
application/json
200 - Voice queue with active agents and waiting engagements200 - Queue with no activity, or unrecognized queue ID — both return zeroed metrics200 - Queue metrics filtered by tags400 - commType is missing400 - queueId is missing400 - Request body could not be parsed403404 - Timed out waiting for initial metrics500503