> For the complete documentation index, see [llms.txt](https://dev.guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.guardian.hedera.com/guardian/standard-registry/policies/tagging/tagging-apis/searching-tag.md).

# Searching Tag

**`POST /api/v1/tags/search`**

Searches for tags associated with one or more target entities of the given type.

**Authentication:** Bearer token required (`Authorization: Bearer <token>`)

**Permission:** `Permissions.TAGS_TAG_READ`

***

## Request

### Request Body

Search for tags on a single target:

```json
{
  "entity": "PolicyDocument",
  "target": "1706823489.123456789"
}
```

Search for tags on multiple targets:

```json
{
  "entity": "PolicyDocument",
  "targets": [
    "1706823489.123456789",
    "1706823490.987654321"
  ]
}
```

| Field         | Type      | Required | Description                                                                                                 |
| ------------- | --------- | -------- | ----------------------------------------------------------------------------------------------------------- |
| `entity`      | string    | Yes      | Entity type to search tags for. One of: `Schema`, `Policy`, `Token`, `Module`, `Contract`, `PolicyDocument` |
| `target`      | string    | No       | Single target message ID. Required if `targets` is not provided                                             |
| `targets`     | string\[] | No       | Array of target message IDs. Required if `target` is not provided                                           |
| `linkedItems` | boolean   | No       | Whether to include linked items in the result                                                               |

***

## Response

### Success Response

**Status:** `200 OK`

Returns a map of target IDs to their associated tag data:

```json
{
  "1706823489.123456789": {
    "entity": "PolicyDocument",
    "target": "1706823489.123456789",
    "refreshDate": "2024-02-01T12:00:00.000Z",
    "tags": [
      {
        "id": "63e3e5e8a01b3c001234abcd",
        "name": "example-tag",
        "entity": "PolicyDocument",
        "target": "1706823489.123456789",
        "owner": "did:hedera:testnet:zHcDLGFNymFAJiMBKnpbHDgjvTn6yZnwkPPeFhtJBECH_0.0.4532001",
        "status": "Published"
      }
    ]
  }
}
```

### Error Responses

| Status                      | Description                                               |
| --------------------------- | --------------------------------------------------------- |
| `401 Unauthorized`          | Missing or invalid token                                  |
| `403 Forbidden`             | Insufficient permissions                                  |
| `422 Unprocessable Entity`  | Missing or invalid `entity`, `target`, or `targets` field |
| `500 Internal Server Error` | Unexpected server failure                                 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.guardian.hedera.com/guardian/standard-registry/policies/tagging/tagging-apis/searching-tag.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.