Create a new config schema.
| Scope | Required |
|---|---|
config_schemas:write | Yes |
The API key to use for authentication.
The API version the client was built against.
"2026-03-09.tetons"
Fields to expand on the config schema resource.
documents, config_type ["documents"]A reference to a config type. At least one of id or slug must be provided. When both are provided, id takes precedence and slug is ignored.
jsonschema, cue "jsonschema"
json, yaml, cue The schema document files.
The file path for config instances created from this schema.
"/v1/motion-control.json"
The git commit to link to this config schema.
Successfully created the config schema.
The object type, which is always config_schema.
config_schema "config_schema"
ID of the config schema.
"cfg_sch_123"
The digest of the config schema.
"sha256:1234567890"
The name of the config type.
"Motion Control"
The file path to deploy the config instance relative to /srv/miru/config_instances. v1/motion-control.json would deploy to /srv/miru/config_instances/v1/motion-control.json.
"/v1/motion-control.json"
Timestamp of when the config schema was created.
"2021-01-01T00:00:00Z"
Timestamp of when the config schema was last updated.
"2021-01-01T00:00:00Z"
ID of the config type.
"cfg_typ_123"
jsonschema, cue "jsonschema"
json, yaml, cue Expand the config schema documents using expand=documents in the query string.
[
{
"id": "doc_123",
"name": "main.json",
"data": "{\n \"$schema\": \"https://json-schema.org/draft/2020-12/schema\",\n \"type\": \"object\"\n}\n"
}
]Expand the config type using 'expand=config_type' in the query string.
{
"object": "config_type",
"id": "cfg_typ_123",
"name": "Motion Control",
"slug": "motion-control",
"created_at": "2021-01-01T00:00:00Z",
"updated_at": "2021-01-01T00:00:00Z",
"created_by_id": "usr_123",
"updated_by_id": "usr_123"
}