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

# Saved lists: Upload a CSV to a saved list

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

## Upload a CSV to a saved list

`POST /v1/saved-lists/{savedListId}/uploads` - operationId `saved-lists.create-upload`

| Permission | Rate limit |
| --- | --- |
| Search edit and the `import` permission | 480 requests a minute per API key |

Adds the rows of a CSV file to one of the workspace's own lists. Kenso checks the file, answers `202` with a
new `csv` source in `pending`, and adds the rows in the background. Poll
`GET /v1/saved-lists/{savedListId}/sources/{sourceId}` until it is `done` or `failed`.

Send `multipart/form-data` with these fields:

- `file`: the CSV, at most 400 MB and 100,000 rows.
- `columnMappings` (optional): a JSON array that maps CSV columns to fields, the same array a contact import
takes, for example
`[{"csvColumn":"Email","targetField":"email"},{"csvColumn":"Deal size","targetField":"custom_variable","customVariableName":"deal_size"}]`.
Without it, Kenso maps the columns by their headers.
- `fixes` (optional): a JSON array of List check fixes, for example `["blocklist","invalidEmail","noMx"]`.
Kenso skips the rows the check flags for each fix. The keys are `blocklist`, `invalidEmail`,
`noMx`, `catchAll`, `personalEmail` and `roleAddress`, as a
`POST /v1/contact-imports/scans` with target `saved_list` reports them. `missingKey` is accepted
and changes nothing.
- `cleanup` (optional): `true` cleans every cell of a field with that field's cleaner before the rows
are added.

`fixes` and `cleanup` need the `csv_import_check` feature on the workspace. A fix skips whole rows:
a row that is already on the list, or that repeats a kept row, still merges into its member with all its
addresses.

When the source is `done`, its `parameters` hold `rowCount`, `inserted`, `merged` and
`rejected`, plus the `fixes` and `cleanup` you sent. `rejected` counts the rows a fix skipped
and the rows that have no LinkedIn URL, no email and no name with a company domain (on a company list, no domain
and no company page). `skips` counts the skipped rows by fix key. Uploaded emails start unverified, Kenso
keeps every phone number, and it never stores personal columns such as birth date, gender, age or personal email.

Errors:

- `400 validation_failed`: the body is not multipart, `file` is missing, empty, not a `.csv`,
larger than 400 MB or longer than 100,000 rows, `columnMappings` or `fixes` is not valid JSON or names an
unknown field or fix, `cleanup` is not `true` or `false`, or `fixes` or `cleanup` came while the
`csv_import_check` feature is off. `error.details` names the field.
- `403 forbidden`: the caller is a workspace key. The upload records the member who added it, and a
workspace key is not a person.
- `404 not_found`: the list is not one of the workspace's own lists, or it is another member's private list.
- `429 rate_limited`: the workspace reached its daily import row quota. Retry after the seconds in the
`Retry-After` header.

Requires Search edit and the `import` permission.

Needs the `saved_lists` 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/saved-lists/POST/v1/saved-lists/%7BsavedListId%7D/uploads)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `savedListId` | path | integer (int64) | yes | The saved list's id. |
| `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`, required.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `file` | string (binary) | yes | The CSV, with a `.csv` name: at most 400 MB and 100,000 rows. |
| `columnMappings` | string | no | A JSON array that maps CSV columns to fields, the same array a contact import takes. Without it, Kenso maps the columns by their headers. |
| `fixes` | string | no | A JSON array of List check fixes, such as `["blocklist","invalidEmail","noMx"]`. Needs the `csv_import_check` feature. |
| `cleanup` | boolean | no | `true` cleans every cell of a field with that field's cleaner. Needs the `csv_import_check` feature. |

### Response 202

`data` is a `SavedListSource`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The source's id. |
| `sourceType` | string, one of: search_filters, search_selection, saved_search, csv, campaign, list, vendor_import, registry, ... | What the source reads. |
| `parameters` | object | The source's settings, for example `{"campaignId": 42}`. A `csv` source holds the upload's details and, once its run is done, `rowCount`, `inserted`, `merged` and `rejected`. An empty object on a shared or library list. |
| `status` | string, one of: pending, running, done, failed | Progress of the source's last run: `pending`, `running`, `done` or `failed`. |
| `statusMessage` | string | Why the run failed, or a note on a finished run, such as the row limit it stopped at. Null otherwise, and on a shared or library list. |
| `addedByUserId` | integer (int64) | The user who added the source. Null when an API key that belongs to no user added it, and on a shared or library list. |
| `lastRefreshedAt` | string (date-time) | When the source's last run finished, in UTC. Null before the first run finishes. |
| `lastRefreshAdded` | integer (int32) | Number of members the source's last run added to the list. |
| `createdAt` | string (date-time) | When the source was added, in UTC. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/saved-lists/812/uploads" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -F "file=@./file" \
  -F 'columnMappings=string' \
  -F 'fixes=string' \
  -F 'cleanup=true'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "sourceType": "search_filters",
    "parameters": null,
    "status": "pending",
    "statusMessage": "string",
    "addedByUserId": 812,
    "lastRefreshedAt": "2026-09-23T15:02:11Z",
    "lastRefreshAdded": 1,
    "createdAt": "2026-09-23T15:02:11Z"
  }
}
```
