# listEmployeeVoices

The voices an AI employee can speak in on calls: `voiceId`, `name`, and `gender`, `accent`, `age` and `description` to match what the person asked for ("a natural woman's voice", "an American accent"). With no `search`, the recommended list its page's voice picker shows first. With `search` (a name or words like "deep" or "british"; `gender` and `accent` narrow it), the matching voices in our voice workspace (`source` ACCOUNT) and then the shared voice library (`source` COMMUNITY), the same search the picker runs. To change the voice, updateEmployeeConfig with `configPatch` `{ channels: { callConfig: { voice: { voiceId } } } }` and one of these ids; the voice's name, gender, accent and sample follow the id, and a library voice is added to the workspace when it is saved. `previewUrl` is a sample the person can play. Only an employee that answers or places calls has a voice (`channels.callConfig` in getEmployee's `configDocument`, whose `voice` is the current one).

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "listEmployeeVoices", "variables": {...} }`
- Scope: `READ`
- Type: query
- Idempotency: a read; rejects `Idempotency-Key`
- Rate-limited: no

## Variables

- `search`: `String`
- `gender`: `String`
- `accent`: `String`

## Response (data, an example)

```json
{
  "aiEmployeesQuery": {
    "recommendedVoices": [
      {
        "voiceId": "…",
        "name": "…",
        "gender": "…",
        "accent": "…",
        "age": "…",
        "description": "…",
        "previewUrl": "…",
        "source": "ACCOUNT"
      }
    ]
  }
}
```

## Example

```bash
curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operationId": "listEmployeeVoices",
    "variables": {}
  }'
```
