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

# Tags: Remove a tag from an entity

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

## Remove a tag from an entity

`DELETE /v1/tags/{tagId}/assignments` - operationId `tags.unassign`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 4,800 requests a minute per API key |

Takes a tag off one entity. Send the fields of assign as query parameters, not a body. The caller needs the same
access as on assign. A deleted tag of the workspace can still come off a `reply`, a
`linkedin_conversation` or an `instagram_conversation`.

Errors:

- `400 validation_failed`: `entityType` is missing or unknown, or its id field is missing.
- `403 permission_denied`: the caller lacks edit access to the entity's page.
- `404 not_found`: the tag or the entity is not in this workspace.

Open to any workspace member.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `tagId` | path | integer (int64) | yes | The tag's id. |
| `entityType` | query | string | no | The entity's type: `campaign`, `contact`, `mailbox`, `domain`, `account`, `linkedin_account`, `person`, `reply`, `linkedin_conversation` or `instagram_conversation`. Required. |
| `entityId` | query | integer (int64) | no | The entity's id. Required for every type except `reply`, `linkedin_conversation` and `instagram_conversation`. |
| `messageId` | query | string | no | For `reply`: the `msg_` id of an email message, as `GET /v1/threads/{threadId}/messages` returns it. |
| `conversationId` | query | string | no | For `linkedin_conversation`: the `thr_` id of a LinkedIn thread, as `GET /v1/threads` returns it. For `instagram_conversation`: the `thr_` id of an Instagram thread (only that id names one). |
| `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`. |
| `Idempotency-Key` | header | string | no | A unique value, such as a UUID, that makes a retry safe. Send the same key when you retry. For 24 hours, a repeat of the same request with the same key gets the first response again, with the `Idempotent-Replayed: true` header, and Kenso does not run the action twice. The same key with a different request answers `422 idempotency_key_reused`. Keys are per workspace and at most 200 characters long. A repeat sent while the first request is still running can get `503 service_unavailable` with `Retry-After`. Retry it with the same key. Kenso does not store a `5xx` response, so a retry after one runs the action again. It does not store a `408`, a `429` or another `4xx` that carries `Retry-After` either: retry with the same key after that time and Kenso runs the action again. |

### Response 200

`data` is a `TagAssignment`.

| Field | Type | Description |
| --- | --- | --- |
| `tagId` | integer (int64) | The tag's id. |
| `entityType` | string | The entity's type: `campaign`, `contact`, `mailbox`, `domain`, `account`, `linkedin_account`, `person`, `reply`, `linkedin_conversation` or `instagram_conversation`. |
| `entityId` | integer (int64) | The entity's id. Null for `reply`, `linkedin_conversation` and `instagram_conversation`. |
| `messageId` | string | For `reply`, the email message id you sent. Null for other types. |
| `conversationId` | string | For `linkedin_conversation` and `instagram_conversation`, the thread id you sent. Null for other types. |

### Request

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

### Example response

```json
{
  "success": true,
  "data": {
    "tagId": 812,
    "entityType": "campaign",
    "entityId": 812,
    "messageId": "msg_ZW1haWw6NDAyMjg0LjJAZXhhbXBsZS5jb20",
    "conversationId": "string"
  }
}
```
