> 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: Update the calling spend limit

> **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).

## Update the calling spend limit

`PATCH /v1/calling/spend-limit` - operationId `calling.spend-limit-update`

| Permission | Rate limit |
| --- | --- |
| The `billing` and `workspace_settings` permissions | 4,800 requests a minute per API key |

Sets `monthlyLimitMillicredits`: 1 to 100,000,000, or null for no limit. The next call checks it; a call that
would pass it gets `402 calling_limit_reached`.

Errors:

- `400 validation_failed`: the field is missing, not a whole number or out of range, or another was sent.

Requires the `workspace_settings` permission and the `billing` permission.

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/PATCH/v1/calling/spend-limit)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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: `object`.

### Response 200

`data` is a `CallingSpendLimit`.

| Field | Type | Description |
| --- | --- | --- |
| `monthlyLimitMillicredits` | integer (int64) | The most calls can spend in a month; null means no limit. |
| `isDefault` | boolean | True while the workspace has never set a limit and uses the default, 2,000 credits a month. |
| `spentThisMonthMillicredits` | integer (int64) | The call minutes and recordings charged this month, plus the credits held for calls in progress: the same spend the limit counts. Phone number fees do not count. |

### Request

```bash
curl -X PATCH "https://api.ken.so/v1/calling/spend-limit" \
  -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 '{}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "monthlyLimitMillicredits": 1,
    "isDefault": true,
    "spentThisMonthMillicredits": 1
  }
}
```
