# Listing of Schema

**`GET /api/v1/schemas`**

Returns a paginated list of all schemas owned by the authenticated Standard Registry user.

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

**Permission:** `Permissions.SCHEMAS_SCHEMA_READ`

***

## Request

### Query Parameters

| Parameter   | Type   | Required | Default | Description                                     |
| ----------- | ------ | -------- | ------- | ----------------------------------------------- |
| `pageIndex` | number | No       | 0       | Zero-based page index (number of pages to skip) |
| `pageSize`  | number | No       | 20      | Number of items to return per page              |
| `category`  | string | No       | —       | Schema category filter (e.g. `POLICY`)          |
| `policyId`  | string | No       | —       | Filter schemas by policy ID                     |
| `moduleId`  | string | No       | —       | Filter schemas by module ID                     |
| `toolId`    | string | No       | —       | Filter schemas by tool ID                       |
| `topicId`   | string | No       | —       | Filter schemas by topic ID                      |

***

## Response

### Success Response

**Status:** `200 OK`

The response includes an `X-Total-Count` header containing the total number of matching schemas.

```json
[
  {
    "id": "63e3e5e8a01b3c001234abcd",
    "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "name": "Carbon Offset Schema",
    "description": "Schema for carbon offset reporting",
    "entity": "VC",
    "status": "PUBLISHED",
    "version": "1.0.0",
    "topicId": "0.0.1234567",
    "owner": "example_user"
  }
]
```

### Error Responses

| Status                      | Description               |
| --------------------------- | ------------------------- |
| `401 Unauthorized`          | Missing or invalid token  |
| `403 Forbidden`             | Insufficient permissions  |
| `500 Internal Server Error` | Unexpected server failure |


---

# Agent Instructions: 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:

```
GET https://guardian.hedera.com/docs/develop/schemas/schema-creation-using-the-guardian-apis/creation-of-a-schema-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.