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

# Domains: Update many domains

> **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 [Domains](/docs/api/domains.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Update many domains

`POST /v1/domains/bulk-update` - operationId `domains.bulk-update`

| Permission | Rate limit |
| --- | --- |
| Delivery edit | 480 requests a minute per API key |

Applies the same changes to up to 1,000 domains in one call, such as turning click tracking on for a group of
domains or giving them all the same tags.

The body is a JSON object with `ids`, a list of 1 to 1,000 domain ids, and at least one field to change.
The fields and their rules are the same as on `PATCH /v1/domains/{domainId}`: `clickRateTrackingEnabled`,
`rampUpDays`, `redirectUrl404`, `tagIds`, `autoRenew` and `websiteMode`. Every domain
gets the same values. Kenso ignores a repeated id.

Kenso updates each domain on its own, so one failed domain does not stop the others. The response gives
`updatedCount`, the number of domains updated, and one `failed` entry with the reason for each domain
that was not, such as an id that is not a domain of this workspace. Example:
`{ "ids": [4, 9], "rampUpDays": 14 }`.

Errors:

- `400 validation_failed`: `ids` is missing, empty or longer than 1,000, the body has no field to change
or an unknown field, or a field has a wrong value.
- `403 permission_denied`: the body changes `autoRenew` and you do not have the `billing` permission.
Nothing is written.
- `404 not_found`: a `tagIds` entry is not a tag of this workspace. Nothing is written.

Requires Delivery edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/domains/POST/v1/domains/bulk-update)

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

| Field | Type | Description |
| --- | --- | --- |
| `updatedCount` | integer (int32) | How many domains Kenso updated without a failure. |
| `failed` | array of DomainBulkFailure | One entry per domain that was not updated, with the reason. Empty when every domain was updated. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/domains/bulk-update" \
  -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": {
    "updatedCount": 1,
    "failed": [
      {
        "id": 812,
        "message": "string"
      }
    ]
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### DomainBulkFailure

A domain that a bulk update could not change.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | integer (int64) | no | The domain's id, as sent in `ids`. |
| `message` | string | no | Why the update failed for this domain. |
