> 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: Hang up 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).

## Hang up a call

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

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

Hangs up both sides of a call you placed. You get `202` with the call's current status, and the call ends
when the carrier confirms. A call that already ended returns `200` with its final status.

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.
- `503 provider_unavailable`: calling is not set up yet.

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/hangup)

### 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`. |

### Response 200

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

| Field | Type | Description |
| --- | --- | --- |
| `callId` | integer (int64) | The call's id. |
| `status` | string | The call's status, such as `bridged`, `completed` or `no_answer`. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/calling/calls/812/hangup" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "callId": 812,
    "status": "bridged"
  }
}
```
