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

# Blocklist: Create a blocklist entry

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

## Create a blocklist entry

`POST /v1/blocklist-entries` - operationId `blocklist-entries.create`

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

Adds one email or domain to the blocklist. From then on, Kenso does not contact that email, or anyone at that
domain.

`type` (`email` or `domain`) and `value` are required. For a domain, a URL works: Kenso keeps
the host without `www.`. `reason` is optional, at most 200 characters.

A domain that a customer account or a blocklist rule already lists, or an email that only a blocklist rule lists,
becomes a `manual` entry under the same id with your reason, and the answer has `claimed: true`. If the
workspace's connected CRM syncs opt-outs, Kenso also marks a newly blocked email as opted out on the matching CRM
contacts. Shared mail provider domains such as gmail.com, hotmail.co.uk and web.de cannot be blocked whole: block
those addresses one by one.

Errors:

- `400 validation_failed`: `type` or `value` is missing or invalid, `reason` is over 200
characters, or the value is already on the blocklist. The existing entry keeps its reason.
- `400 validation_failed` with detail code `shared_mail_provider`: the domain is a shared mail provider.

Requires the `workspace_settings` permission.

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

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

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | string | yes | What to block: `email` for one address, `domain` for every address at a domain. Required. |
| `value` | string | yes | The email address or domain to block. Required. For a domain, a URL works: Kenso keeps the host without `www.`. |
| `reason` | string | no | Why the value is blocked. Optional, at most 200 characters. Blank stores no reason. |

### Response 201

`data` is a `BlocklistEntry`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The entry's id. |
| `type` | string | What the entry blocks: `email` for one address, `domain` for every address at a domain. |
| `value` | string | The blocked email or domain, in lowercase, such as `jane@acme.com` or `acme.com`. |
| `createdAt` | string (date-time) | When the entry was added, in UTC. Null in a bulk create result. |
| `source` | string | Where the entry came from: `manual`, `own_domain`, `customer` or `rule`. A `manual` entry was added by a member, through the API or a CSV file, or by Kenso after an opt-out or a bounce. An `own_domain` entry is one of the workspace's own domains, and it goes away when you remove the domain in Settings > Company. A `customer` entry is the domain of an account marked a customer, and it goes away when the account stops being a customer. A `rule` entry comes from a blocklist rule, and it goes away once no enabled rule matches it. Adding a `customer` or `rule` value yourself makes it `manual`. |
| `reason` | string | Why the value is blocked, at most 200 characters. Omitted when the entry has none. Kenso sets a reason on the entries it adds, such as `Opted out or bounced` or `Customer account`. Own-domain entries have none. |
| `claimed` | boolean | True in a create or bulk create result when a customer account or a blocklist rule already listed the value and the call made that entry `manual`, under the same id. Omitted otherwise. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/blocklist-entries" \
  -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 '{
  "type": "domain",
  "value": "competitor.example.com",
  "reason": "Current customer"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 7712,
    "type": "domain",
    "value": "competitor.example.com",
    "createdAt": "2026-09-23T15:02:11Z",
    "source": "manual",
    "reason": "Current customer"
  }
}
```
