> 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/develop/guardian/standard-registry/roles-and-permissions/apis-related-to-roles-and-permissions/returns-list-of-all-policies.md).

# Returns list of all Policies

**`GET /api/v1/permissions/users/{username}/policies`**

Returns a paginated list of policies accessible to the specified user.

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

**Permission:** `Permissions.PERMISSIONS_ROLE_MANAGE` or `Permissions.DELEGATION_ROLE_MANAGE`

***

## Request

### Path Parameters

| Parameter  | Type   | Required | Description              |
| ---------- | ------ | -------- | ------------------------ |
| `username` | string | Yes      | Target user's login name |

### Query Parameters

| Parameter   | Type   | Required | Default | Description                                                        |
| ----------- | ------ | -------- | ------- | ------------------------------------------------------------------ |
| `pageIndex` | number | No       | 0       | Zero-based page index                                              |
| `pageSize`  | number | No       | 20      | Items per page                                                     |
| `status`    | string | No       | —       | Filter by policy status (e.g., `DRAFT`, `PUBLISH`, `DISCONTINUED`) |

***

## Response

### Success Response

**Status:** `200 OK`

The total count of matching policies is returned in the `X-Total-Count` response header.

```json
[
  {
    "id": "63e3e5e8a01b3c001234abcd",
    "name": "Carbon Credits Policy",
    "version": "1.0.0",
    "status": "PUBLISH",
    "owner": "did:hedera:testnet:zHcDLGFNymFAJiMBKnpbHDgjvTn6yZnwkPPeFhtJBECH_0.0.4532001"
  }
]
```

| Field     | Type   | Description                                       |
| --------- | ------ | ------------------------------------------------- |
| `id`      | string | Policy identifier                                 |
| `name`    | string | Policy name                                       |
| `version` | string | Policy version                                    |
| `status`  | string | Current policy status                             |
| `owner`   | string | DID of the Standard Registry that owns the policy |

### Error Responses

| Status                      | Description                                                |
| --------------------------- | ---------------------------------------------------------- |
| `401 Unauthorized`          | Missing or invalid token                                   |
| `403 Forbidden`             | Insufficient permissions                                   |
| `404 Not Found`             | User does not exist or is not under this Standard Registry |
| `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://guardian.hedera.com/docs/develop/guardian/standard-registry/roles-and-permissions/apis-related-to-roles-and-permissions/returns-list-of-all-policies.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.