Skip to main content
GET
Get

Authorizations

X-API-Key
string
header
required

The API key to use for authentication.

Headers

Miru-Version
string
required

The API version the client was built against.

Example:

"2026-10-28.everglades"

Path Parameters

config_schema_id
string
required

The unique identifier of the config schema.

Example:

"cfg_sch_123"

Query Parameters

expand
enum<string>[]

Fields to expand on the config schema resource.

Available options:
documents,
config_type
Example:

Response

200 - application/json

Successfully retrieved the config schema.

object
enum<string>
required

The object type, which is always config_schema.

Available options:
config_schema
Example:

"config_schema"

id
string
required

ID of the config schema.

Example:

"cfg_sch_123"

digest
string
required

The digest of the config schema.

Example:

"sha256:1234567890"

os
enum<string>
required

The operating system family this config schema targets, derived from its instance slot filepaths, which must all agree. A schema created without instance_slots gets a default slot at a Unix path, so it is linux. Read-only: clients cannot set it.

Available options:
linux,
windows
Example:

"linux"

config_type_name
string
required

The name of the config type.

Example:

"Motion Control"

instance_slots
Instance Slot · object[]
required

The file system destinations this config schema writes to. Every config schema has at least one slot. Slots share the schema's validation and differ only in where the file is written; a file needing different validation is a different config type, not a slot. Slot keys and filepaths must each be unique within the schema, and slot filepaths must be unique across every config schema in a release.

Minimum array length: 1
Example:
instance_format
enum<string>
required

The serialization format of config content. A config instance is written to the device filesystem in this format.

  • json: standard JSON.
  • yaml: YAML 1.2.
  • jsonc: JSON with comments (JSON plus // and /* */ comment syntax).
  • xml: XML.
  • csv: comma-separated values (RFC 4180).
  • text: plain, unstructured text with no specific format.
Available options:
json,
yaml,
jsonc,
xml,
csv,
text
created_at
string<date-time>
required

Timestamp of when the config schema was created.

Example:

"2021-01-01T00:00:00Z"

updated_at
string<date-time>
required

Timestamp of when the config schema was last updated.

Example:

"2021-01-01T00:00:00Z"

config_type_id
string
required

ID of the config type.

Example:

"cfg_typ_123"

language
enum<string>
required
Available options:
jsonschema,
cue,
opaque
Example:

"jsonschema"

format
enum<string>
required
Available options:
json,
yaml,
cue
documents
Schema Document · object[]

Expand the config schema documents using expand=documents in the query string.

Example:
config_type
Config Type · object

Expand the config type using 'expand=config_type' in the query string.

Example: