https://docs.test.geena.eu/reference/index.html Reference Enums — all enum values referenced in the User API. Error codes — HTTP and GraphQL error shapes. Built-in schemas — catalog of the 24 shipped JSON schemas (schemaRef values, fields, scope). Embedded schemas — using the documentSchema field: validation pipeline, supported JSON Schema features, $ref to built-ins, composition patterns. Hugo en https://docs.test.geena.eu/reference/enums/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/reference/enums/index.html Enums All enum types referenced from the User API. SharedVaultTemplate Controls which schemas are pre-installed when a shared vault is created. Value Use case LEGAL_ENTITY Corporate / UBO collection CUSTOM No pre-installed schemas PERSONAL Personal data collection SharedVaultCollaboratorRole Returned by SharedVault.myRole: https://docs.test.geena.eu/reference/error-codes/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/reference/error-codes/index.html Error codes Transport errors (plain HTTP) Returned by Echo / the auth middleware before the request reaches GraphQL. Body is {"message":"..."} plain JSON. HTTP Message Where 400 invalid request body auth endpoints, body parse failure 400 invalid email format /auth/send-otp, /auth/verify-email/* 400 email and code are required /auth/verify-otp, /auth/verify-email/confirm 401 Missing token auth middleware — no Authorization header 401 Invalid token auth middleware — bad signature, expired, session missing/revoked 401 invalid or expired code OTP verification — no active OTP or wrong code 401 invalid session /auth/renew, /auth/verify-email/* — session context missing 429 too many OTP requests more than 3 OTP sends per email in the last hour 429 too many verification requests for this email same limit on /auth/verify-email/send 429 too many verification attempts OTP consumed 5 wrong attempts 500 failed to create session / failed to create token infrastructure failure during login 500 failed to renew session / failed to record email verification infrastructure failure 503 unable to send verification code, please try again email service unreachable GraphQL errors Any error from a resolver comes back in the standard GraphQL envelope: https://docs.test.geena.eu/reference/schemas/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/reference/schemas/index.html Built-in schemas The backend ships with 24 built-in JSON schemas used to validate DocumentInput.data payloads. They cover personal, corporate, and platform-service data shapes. Canonical schemaRef format Every built-in schema has a canonical reference URL: https://schema.identa.io/core/{SchemaName}.json Use this URL verbatim as DocumentInput.schemaRef when creating documents. The backend resolves it to the embedded JSON Schema at write time and validates data against it. https://docs.test.geena.eu/reference/embedded-schemas/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/reference/embedded-schemas/index.html Embedded documentSchema DocumentInput accepts either a schemaRef (pointer to a built-in schema) or an embedded JSON Schema body via documentSchema. This page documents how documentSchema is handled server-side, what JSON Schema features are supported, and the composition patterns that work. input DocumentInput { name: String! schemaRef: String # option A — one of the built-ins documentSchema: JSON # option B — inline JSON Schema (Draft 2020-12) description: String uniquePerVault: Boolean data: JSON! } schemaRef vs documentSchema — which do I use? Situation Use Data matches a single built-in exactly schemaRef Need to combine several built-ins (e.g. name+address) documentSchema (with $ref) Need extra required fields on top of a built-in documentSchema (allOf + required) Need fields that no built-in covers documentSchema One-off document tied to a specific flow or app documentSchema Warning Mutual exclusion is enforced. Providing neither returns a “no schema definition” error; providing both returns “both schema definitions”. The check lives in DocumentMetadata.ValidateSchemaDefinition() in the domain layer (pkg/domain/document.go).