> 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/schema-creation-using-the-guardian-apis/updating-schema.md).

# Updating Schema

**`PUT /api/v1/schemas`**

Updates an existing schema. The schema to update is identified by the `id` field in the request body. Only users with the Standard Registry role are allowed to make this request. Published or demo-mode schemas cannot be updated.

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

**Permission:** `Permissions.SCHEMAS_SCHEMA_UPDATE`

***

## Request

### Request Body

```json
{
  "id": "63e3e5e8a01b3c001234abcd",
  "name": "Updated Carbon Offset Schema",
  "description": "Updated description for carbon offset reporting",
  "entity": "VC",
  "category": "POLICY",
  "document": {
    "$schema": "http://json-schema.org/draft-07/schema",
    "type": "object",
    "properties": {}
  }
}
```

| Field         | Type   | Required | Description                                  |
| ------------- | ------ | -------- | -------------------------------------------- |
| `id`          | string | Yes      | Internal database ID of the schema to update |
| `name`        | string | No       | Updated human-readable name                  |
| `description` | string | No       | Updated description                          |
| `entity`      | string | No       | Schema entity type                           |
| `category`    | string | No       | Schema category                              |
| `document`    | object | No       | Updated JSON Schema document                 |

***

## Response

### Success Response

**Status:** `200 OK`

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

### Error Responses

| Status                      | Description                                                 |
| --------------------------- | ----------------------------------------------------------- |
| `401 Unauthorized`          | Missing or invalid token                                    |
| `403 Forbidden`             | Insufficient permissions or schema is owned by another user |
| `404 Not Found`             | Schema with the provided ID does not exist                  |
| `422 Unprocessable Entity`  | Schema is already published or imported in demo mode        |
| `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/schema-creation-using-the-guardian-apis/updating-schema.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.