The Get supervisors assigned for a queue endpoint returns the supervisors assigned to a specific inbound routing queue.

Requirements: Base URL, Authentication, Error codes

Scope: routing.queues.read

What this does

When you send a Get supervisors assigned for a queue request with a queue ID, Voiso returns a paginated list of supervisors for that queue.

When to use it

Display or sync queue supervisor assignments in an external system
Build an admin UI that shows who supervises a queue
Validate routing configuration during audits or troubleshooting

Prerequisites

The queue must exist in the contact center.
You must have access to the queue.

Endpoint


GET /api/v4/routing/queues/{queue_id}/supervisors

Request parameters

Path parameters

queue_id
The unique identifier of the queue.

Query parameters

All query parameters are optional.

limit
The number of items to return. Default is 100. Maximum is 100.
offset
The number of items to skip before collecting results. Default is 0.

Examples

Minimal request

curl -X GET "https://{cluster_id}.voiso.com/api/v4/routing/queues/1/supervisors" \
  -H "Authorization: Bearer <contact_center_api_key>" \
  -H "Content-Type: application/json"

Request the second page of results (50 per page)

curl -X GET "https://{cluster_id}.voiso.com/api/v4/routing/queues/1/supervisors?limit=50&offset=50" \
  -H "Authorization: Bearer <contact_center_api_key>" \
  -H "Content-Type: application/json"

Response

If successful, the API returns an array of user objects and pagination metadata.

{
  "users": [
    {
      "id": "0b97ce11-b6e0-49b4-8f92-68040aa324bf",
      "name": "Jane Doe",
      "email": "jane.doe@companyname.com",
      "sip_account": "jane.doe@contactcenter.com",
      "extension": "102",
      "caller_id": "12025550123",
      "employee_id": "E-482",
      "timezone": "America/New_York",
      "security_access_group": {
        "id": 3,
        "name": "Boarding"
      },
      "teams": [
        {
          "id": 3,
          "name": "Multilingual Support"
        }
      ],
      "supervised_teams": [
        {
          "id": 3,
          "name": "Multilingual Support"
        }
      ],
      "queues": [
        {
          "id": 1,
          "name": "Technical Support"
        }
      ],
      "supervised_queues": [
        {
          "id": 1,
          "name": "Technical Support"
        }
      ],
      "webrtc_ringtone": {
        "type": "ringtone",
        "name": "Bells (Default)"
      },
      "channels": [
        "voice",
        "chat",
        "whatsapp"
      ],
      "channel_group_capacity": {
        "chat": 5,
        "instant": 3
      },
      "channel_profiles": [
        {
          "id": 12,
          "channel": "whatsapp",
          "identifier": "18885658889",
          "name": "WhatsApp Main (18885658889)"
        }
      ],
      "speech_language": "en",
      "skills": [
        {
          "skill": {
            "id": 1,
            "name": "Sales"
          },
          "value": 5
        }
      ],
      "status": "available",
      "created_at": "2025-11-11T12:00:00.216Z",
      "updated_at": "2025-11-11T12:00:00.216Z",
      "deleted_at": "2025-11-11T12:00:00.216Z"
    }
  ],
  "metadata": {
    "total": 100
  }
}

Next steps

Retrieve queue details: Get queue
Retrieve queue members: Get queue users

Troubleshooting

401 Unauthorized

What to check:

You are sending Authorization: Bearer <contact_center_api_key>.
Your Base URL includes the correct {cluster_id}.

403 Forbidden

What to check:

The API key is valid, but does not have access to this queue.

404 Not found

This usually means the queue ID does not exist, or you do not have access to it.

What to check:

Confirm the queue ID using Get queues.

429 Too many requests

What to do:

Reduce request frequency and retry with backoff.