> 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/schemas/system-schemas-apis/returns-schema-by-username.md).

# Returns Schema by Username

**`GET /schemas/system/{username}`**

Returns a paginated list of all system schemas for the specified user. Only users with the Standard Registry role are allowed to make this request.

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

**Permission:** `Permissions.SCHEMAS_SYSTEM_SCHEMA_READ`

***

## Request

### Path Parameters

| Parameter  | Type   | Required | Description                  |
| ---------- | ------ | -------- | ---------------------------- |
| `username` | string | Yes      | Username of the schema owner |

### Query Parameters

| Parameter   | Type   | Required | Default | Description           |
| ----------- | ------ | -------- | ------- | --------------------- |
| `pageIndex` | number | No       | 0       | Zero-based page index |
| `pageSize`  | number | No       | 25      | Items per page        |

***

## Response

### Success Response

**Status:** `200 OK`

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

```json
[
  {
    "id": "63e3e5e8a01b3c001234abcd",
    "name": "Example System Schema",
    "entity": "STANDARD_REGISTRY",
    "status": "PUBLISHED",
    "system": true,
    "active": true,
    "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
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/schemas/system-schemas-apis/returns-schema-by-username.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.