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

# Contact exports: Download a contact export

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

## Download a contact export

`GET /v1/contact-exports/{exportId}/content` - operationId `contact-exports.content`

| Permission | Rate limit |
| --- | --- |
| Campaigns view and the `export` permission | 240 requests a minute per API key |

Streams the export's file. This is the path in the job's `downloadUrl`. Kenso builds the file at each
download from what you set when you created the export, so the rows reflect your contacts at that moment.

The file is a CSV. A kind `campaign` export of a campaign with more than one active segment is a ZIP with one
CSV per segment. A kind `events` file has the columns `eventId`, `eventType`, `timestamp` and
`contactId`. A cell that starts like a spreadsheet formula gets a leading apostrophe.

Each download charges its rows to the workspace's daily export row limit. You can download an export for 24 hours
after you create it.

Errors:

- `400 validation_failed`: Kenso cannot build the file, for example a kind `clicked` export of a campaign with no clicks, a kind `campaign` export without `fields` of a campaign with no personalization prompts, or a kind `contacts` export that now matches more than 50,000 contacts.
- `404 not_found`: no export with this id exists in the workspace, or it is older than 24 hours.
- `429 quota_exceeded`: the file would hold more than 50,000 rows.
- `429 rate_limited`: the workspace reached its daily export row limit.

Requires Campaigns view and the `export` permission.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/contact-exports/GET/v1/contact-exports/%7BexportId%7D/content)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `exportId` | path | integer (int64) | yes | The export's id, the same as the id of its `contact_export` job. |
| `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`. |

### Response 200

The body is a `string (binary)`.

### Request

```bash
curl -X GET "https://api.ken.so/v1/contact-exports/812/content" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
"<binary>"
```
