> 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: Get a tag

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

## Get a tag

`GET /v1/tags/{tagId}` - operationId `tags.get`

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

Returns one tag of the workspace by its id.

Errors:

- `404 not_found`: no tag of this workspace has the id, or the tag was deleted.

Open to any workspace member.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `tagId` | path | integer (int64) | yes | The tag's id, as `GET /v1/tags` returns 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

`data` is a `Tag`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The tag's id. |
| `name` | string | The tag's name, unique in the workspace ignoring case. |
| `description` | string | A note on what the tag means. Null when the tag has none. |
| `color` | string | The tag's color, as a hex value such as `#E4D0FF` or an `rgba(...)` value. |
| `type` | string | The tag's main entity type, such as `campaign`. Read `entityTypes` for every type Kenso offers the tag on. |
| `entityTypes` | array of string | Where Kenso offers the tag: any of `campaign`, `contact`, `mailbox`, `domain`, `reply`, `account`, `linkedin_account` and `person`. A system tag or sender configuration tag can go only on these types. Any other tag can go on every type. |
| `isConfig` | boolean | True for a sender configuration tag, which groups mailboxes and domains. Like a system tag, it can go only on the types in `entityTypes`. |
| `isSystem` | boolean | True for a system tag that Kenso owns, such as a reply classification. You cannot change or delete it. |
| `systemKey` | string | The stable key of a system tag, such as `champion` or `reply_interested`. Use it to find a system tag instead of its name. Null for other tags. |
| `createdAt` | string (date-time) | When the tag was created, in UTC. |
| `updatedAt` | string (date-time) | When the tag last changed, in UTC. |
| `usage` | TagUsage | How many entities carry the tag. Present only with `includeUsage=true`. |
| `entityIds` | array of integer (int64) | The ids of the workspace's campaigns that carry the tag, in ascending order, deleted campaigns left out. Present only with `entityType=campaign` and `includeEntityIds=true`. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/tags/812" \
  -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": {
    "id": 341,
    "name": "Hot lead",
    "description": "Asked for a call or pricing",
    "color": "#FFD6A5",
    "type": "contact",
    "entityTypes": [
      "contact",
      "reply"
    ],
    "isConfig": false,
    "isSystem": false,
    "createdAt": "2026-09-23T15:02:11Z",
    "updatedAt": "2026-10-14T09:41:27Z"
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### TagUsage

How many entities of the workspace carry a tag. Deleted entities do not count.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `campaignCount` | integer (int32) | no | Campaigns that carry the tag. |
| `contactCount` | integer (int32) | no | Contacts that carry the tag. |
| `replyCount` | integer (int32) | no | Email replies (messages) that carry the tag. |
| `linkedinConversationCount` | integer (int32) | no | LinkedIn conversations that carry the tag. |
| `inboxCount` | integer (int32) | no | Mailboxes that carry the tag. |
| `domainCount` | integer (int32) | no | Domains that carry the tag. |
| `accountCount` | integer (int32) | no | Accounts that carry the tag. |
| `linkedinAccountCount` | integer (int32) | no | LinkedIn accounts that carry the tag. |
