# Export Schema Message IDs

**`GET /api/v1/schemas/{schemaId}/export/message`**

Returns the Hedera message ID of the published schema. The message contains the IPFS CID of the schema file. Only users with the Standard Registry role are allowed to make this request.

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

**Permission:** `Permissions.SCHEMAS_SCHEMA_READ`

***

## Request

### Path Parameters

| Parameter  | Type   | Required | Description                                      |
| ---------- | ------ | -------- | ------------------------------------------------ |
| `schemaId` | string | Yes      | The internal database ID of the schema to export |

***

## Response

### Success Response

**Status:** `200 OK`

```json
{
  "id": "63e3e5e8a01b3c001234abcd",
  "name": "Carbon Offset Schema",
  "description": "Schema for carbon offset reporting",
  "version": "1.0.0",
  "messageId": "1234567890.000000001",
  "owner": "example_user"
}
```

### Error Responses

| Status                      | Description                                        |
| --------------------------- | -------------------------------------------------- |
| `401 Unauthorized`          | Missing or invalid token                           |
| `403 Forbidden`             | Insufficient permissions                           |
| `422 Unprocessable Entity`  | Schema cannot be exported (e.g. not yet published) |
| `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/export-a-schema.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.