schemas

user.schema

The User scope exposes the backend’s schema registry so clients can discover which built-in schemas are available and fetch their JSON Schema definitions at runtime. Use these when rendering forms, validating data locally, or picking a schemaRef for document.create.

For a human-readable catalog of what each schema means, see reference/schemas.

Auth

Bearer JWT. Vault can be sealed — the registry is not encrypted.

user.schema.list

Returns every schema known to the server (all 24 built-in schemas, plus any service schemas added at runtime).

query {
  user {
    schema {
      list {
        metadata { ref scope name description }
      }
    }
  }
}

user.schema.get

Fetches one schema, including the full JSON Schema body.

query($ref: String!) {
  user {
    schema {
      get(ref: $ref) {
        metadata { ref scope name description }
        content  { schema }
      }
    }
  }
}

ref is the canonical URL form, e.g. https://schema.identa.io/core/PersonFullName.json.

curl

curl -X POST https://api.test.geena.eu/graphql \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query($r: String!) { user { schema { get(ref: $r) { metadata { scope name } content { schema } } } } }",
    "variables": { "r": "https://schema.identa.io/core/PersonFullName.json" }
  }'