> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/calling/openapi.json](/docs/api/calling/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Calling: Drop a voicemail greeting on a call

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Calling](/docs/api/calling.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Drop a voicemail greeting on a call

`POST /v1/calling/calls/{callId}/voicemail-drop` - operationId `calling.calls-voicemail-drop`

| Permission | Rate limit |
| --- | --- |
| Accounts edit | 4,800 requests a minute per API key |

Leaves one of your recorded greetings on the person's voicemail. Send `voicemailId`, or leave it out to use
your oldest greeting. The call must be one you placed, the other side must have answered, and the call's
`voicemailDropMode` must not be `off`.

Kenso waits for the voicemail beep, hangs up your side, plays the greeting and then hangs up. The call is logged
with the `voicemail` outcome. When Kenso heard a person rather than a machine, no beep comes and the greeting
plays at once, so ask for the drop after you hear the beep. Do not hang up the call after a drop: that cuts the
greeting off.

You get `202` with `voicemailDropStatus` `requested`, `starting`, `playing` or
`failed`, and `200` once it is `dropped`. Asking again while a drop is under way returns its state.

Errors:

- `403 forbidden`: you did not place this call, or the API key is not tied to a member.
- `404 not_found`: no call started in Kenso has this id in the workspace, or `voicemailId` is not one of
your greetings.
- `409 invalid_state`: the call ended, nobody has answered yet, or voicemail drops are off for it.
- `409 no_voicemail`: you sent no `voicemailId` and have no greeting.
- `503 provider_unavailable`: calling or Kenso's audio storage is not set up yet.
- `503 try_again`: the call is busy. Retry after the `Retry-After` header.

Requires Accounts edit.

Needs the `calling` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/calling/POST/v1/calling/calls/%7BcallId%7D/voicemail-drop)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `callId` | path | integer (int64) | yes | The call's id, from the response that started it. |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `voicemailId` | integer (int64) | no | One of your greetings. Leave it out to drop your oldest. |

### Response 200

Also answers `202`. `data` is a `CallingVoicemailDrop`.

| Field | Type | Description |
| --- | --- | --- |
| `callId` | integer (int64) | The call's id. |
| `voicemailId` | integer (int64) | The greeting being dropped. |
| `voicemailDropStatus` | string | Where the drop is: `requested` (waiting for the beep, which never comes when Kenso heard a person rather than a machine: the greeting then plays at once), `starting` (Kenso is hanging up your side), `playing`, `dropped` or `failed`. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/calling/calls/812/voicemail-drop" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "voicemailId": 812
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "callId": 812,
    "voicemailId": 812,
    "voicemailDropStatus": "string"
  }
}
```
