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

# Attachments

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

Upload a file to attach to an outgoing message, download attachments and delete unsent ones.

Inbox. 3 endpoints under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/attachments/openapi.json](/docs/api/attachments/openapi.json).

- `POST /v1/attachments` - Upload an attachment (`attachments.create`): [/docs/api/attachments/create.md](/docs/api/attachments/create.md)
- `DELETE /v1/attachments/{attachmentId}` - Delete an attachment (`attachments.delete`): [/docs/api/attachments/delete.md](/docs/api/attachments/delete.md)
- `GET /v1/attachments/{attachmentId}/content` - Download an attachment (`attachments.get-content`): [/docs/api/attachments/get-content.md](/docs/api/attachments/get-content.md)

## Upload an attachment

`POST /v1/attachments` - operationId `attachments.create`

| Permission | Rate limit |
| --- | --- |
| Inbox edit | 4,800 requests a minute per API key |

Uploads a file to send with an email reply or forward. The file stays pending until a reply or forward sends it.

Send the request as `multipart/form-data` with the file in `file` and the email message in
`messageId`. Use the thread's newest message, the last one `GET /v1/threads/{threadId}/messages` lists:
a reply or forward takes only files uploaded against that message. Allowed file types are PDF, JPEG, PNG, GIF,
WebP, DOCX, XLSX, PPTX, TXT and CSV. Kenso checks that the file's content matches its extension. One message takes
at most 5 pending files, 8 MiB per file and 10 MiB together.

Errors:

- `400 validation_failed`: `messageId` is not an email message id, `file` is missing or empty,
the file type is not allowed, or the file breaks a size or count limit.
- `404 not_found`: the message is not in this workspace.

An image for an Instagram reply is uploaded with `purpose=instagram` and no `messageId`, while the
workspace has Instagram on (otherwise `404`): one PNG, JPEG or WebP image of at most 5 MB. The `att_` id
goes in an Instagram reply's `attachmentIds`; an image no reply takes is never sent, and it cannot be deleted.

Requires Inbox edit.

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

### 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 file to upload, as a multipart file part. |
| `messageId` | string | no | The `msg_` id of the email message the file is for. LinkedIn message ids are refused. |
| `purpose` | string | no | `instagram` for an Instagram reply's image, sent without `messageId`. Omit it for email. |

### Response 201

`data` is a `Attachment`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | string | The file's `att_` id. Pass it in `attachmentIds` on a reply or forward. |
| `messageId` | string | The `msg_` id of the email message the file was uploaded against. Empty for an Instagram image. |
| `fileName` | string | The file name without any folder path, control characters or quotes. |
| `contentType` | string | The MIME type Kenso read from the file's content, such as `application/pdf`. |
| `sizeBytes` | integer (int64) | The file size in bytes. |

### Request

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

### Example response

```json
{
  "success": true,
  "data": {
    "id": "att_2bX9kq4LmR7tW3vY",
    "messageId": "msg_ZW1haWw6NDAyMjg0LjJAZXhhbXBsZS5jb20",
    "fileName": "string",
    "contentType": "application/pdf",
    "sizeBytes": 1
  }
}
```

## Delete an attachment

`DELETE /v1/attachments/{attachmentId}` - operationId `attachments.delete`

| Permission | Rate limit |
| --- | --- |
| Inbox edit | 4,800 requests a minute per API key |

Removes an uploaded file that no reply or forward has taken yet. Returns `204` with no body.

Errors:

- `400 validation_failed`: a reply or forward already took the file, so it can no longer be removed.
- `404 not_found`: the id is malformed, or no pending upload in this workspace has it.

Requires Inbox edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/attachments/DELETE/v1/attachments/%7BattachmentId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `attachmentId` | path | string | yes | The `att_` id that `POST /v1/attachments` returned. |
| `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 204

### Request

```bash
curl -X DELETE "https://api.ken.so/v1/attachments/att_ZW1haWw6NDAyMjg0LjJAZXhhbXBsZS5jb206MQ" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```http
HTTP/1.1 204 No Content
```

## Download an attachment

`GET /v1/attachments/{attachmentId}/content` - operationId `attachments.get-content`

| Permission | Rate limit |
| --- | --- |
| Inbox view | 12,000 requests a minute per API key |

Returns the file's bytes with its content type. Get the `att_` id from the `attachments` of a message
in `GET /v1/threads/{threadId}/messages`.

By default the response is a download with the file's name. With `inline=true` Kenso serves an inline image
for display in the page instead.

A WhatsApp file (an image or voice note on a WhatsApp thread) comes from WhatsApp each time; Kenso does not keep
it. Its download is named `whatsapp-{id}` with the type's extension, and `inline=true` serves JPEG, PNG,
GIF, WebP and audio inline.

Errors:

- `404 not_found`: the id is malformed, the file is not in this workspace, Kenso no longer has the original
email, or `inline=true` names a file that is not an inline image.
- `503 service_unavailable`: Instagram or WhatsApp could not serve the file right now.

An Instagram file (an uploaded image, or an image or voice note in an Instagram chat) is served only while the
workspace has Instagram on and the chat is visible. A chat's file comes from Instagram each time; Kenso does not
keep it. `inline=true` serves images and audio inline, and every other type downloads.

Requires Inbox view.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `attachmentId` | path | string | yes | The `att_` id of the file. |
| `inline` | query | boolean | no | True to serve an inline image for display instead of as a download. Only inline images (JPEG, PNG, GIF, WebP and BMP) accept it. |
| `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/attachments/att_ZW1haWw6NDAyMjg0LjJAZXhhbXBsZS5jb206MQ/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>"
```

All resources: [/docs.md](/docs.md).
