> 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: Import blocklist entries from a CSV file

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

## Import blocklist entries from a CSV file

`POST /v1/blocklist-entries/imports` - operationId `blocklist-entries.import`

| Permission | Rate limit |
| --- | --- |
| The `workspace_settings` permission | 480 requests a minute per API key |

Adds the rows of a CSV file to the blocklist. Kenso processes the whole file before it answers.

Send `multipart/form-data` with the field `file`: a `.csv` file with a CSV content type such as
`text/csv`, with an `email` column, a `domain` column or both, and an optional `reason`
column. A file holds at most 100,000 rows. A reason cell over 200 characters is cut and never fails the file. The optional form field
`reason`, at most 200 characters, applies to every row without its own.

Rows already on the blocklist keep their own reason. A shared mail provider in the `domain` column, such as
gmail.com, is skipped. Imported emails are not sent to the connected CRM as opt-outs. Kenso adds the rows in file
order and stops at the first row with an invalid email or domain: the rows before it stay on the blocklist.

Errors:

- `400 validation_failed`: `file` is missing, empty, not a CSV file or over 100,000 rows,
`reason` is over 200 characters, or a row holds an invalid email or domain. The message names the row.

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

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

`multipart/form-data`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `file` | string (binary) | no | The CSV file, with an `email` column, a `domain` column or both, and an optional `reason` column. |
| `reason` | string | no | The reason for every row without its own. Optional, at most 200 characters. |

### Response 200

`data` is a `BlocklistImport`.

| Field | Type | Description |
| --- | --- | --- |
| `status` | string | Always `succeeded`: Kenso processed every row of the file before it answered. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/blocklist-entries/imports" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -F "file=@./file" \
  -F 'reason=string'
```

### Example response

```json
{
  "success": true,
  "data": {
    "status": "string"
  }
}
```
