> For the complete documentation index, see [llms.txt](https://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://guardian.hedera.com/docs/3.7.0/developer-tools-and-resources/api-reference/apis-related-2/returns-the-list-of-messages-for-the-target-discussion.md).

# Returns the list of messages for the target discussion

**`POST /api/v1/policy-comments/{policyId}/{documentId}/discussions/{discussionId}/comments/search`**

Returns the paginated list of messages for the target discussion.

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

**Permission:** `Permissions.POLICIES_POLICY_EXECUTE`, `Permissions.POLICIES_POLICY_MANAGE`, or `Permissions.POLICIES_POLICY_AUDIT`

***

## Request

### Path Parameters

| Parameter      | Type   | Required | Description           |
| -------------- | ------ | -------- | --------------------- |
| `policyId`     | string | Yes      | Policy identifier     |
| `documentId`   | string | Yes      | Document identifier   |
| `discussionId` | string | Yes      | Discussion identifier |

### Query Parameters

| Parameter  | Type    | Required | Default | Description                                                         |
| ---------- | ------- | -------- | ------- | ------------------------------------------------------------------- |
| `readonly` | boolean | No       | false   | When `true` and the caller has audit permission, enables audit mode |

### Request Body

```json
{
  "pageIndex": 0,
  "pageSize": 25,
  "from": "2026-01-01T00:00:00.000Z"
}
```

| Field       | Type   | Required | Description                                             |
| ----------- | ------ | -------- | ------------------------------------------------------- |
| `pageIndex` | number | No       | Zero-based page index                                   |
| `pageSize`  | number | No       | Number of items per page                                |
| `from`      | string | No       | Filter comments created after this timestamp (ISO 8601) |

***

## Response

### Success Response

**Status:** `200 OK`

The response includes an `X-Total-Count` header with the total number of messages.

```json
[
  {
    "id": "63e3e5e8a01b3c001234abcd",
    "message": "The capacity figure should be 50 MWh — the extra zero appears to be a typo.",
    "owner": "did:hedera:testnet:zHcDLGFNymFAJiMBKnpbHDgjvTn6yZnwkPPeFhtJBECH_0.0.4532001",
    "createDate": "2026-03-30T10:05:00.000Z",
    "files": []
  }
]
```

### Error Responses

| Status                      | Description               |
| --------------------------- | ------------------------- |
| `401 Unauthorized`          | Missing or invalid token  |
| `403 Forbidden`             | Insufficient permissions  |
| `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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/3.7.0/developer-tools-and-resources/api-reference/apis-related-2/returns-the-list-of-messages-for-the-target-discussion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
