Edit schema
Proposes a schema/mapping change for a subtype you’ve already registered.
PATCH
api:org-config
Always opens a new pending request targeting the next version — never mutates an active version in place. Editing an already-active subtype defaults any field you omit to what’s currently active, so the reviewer sees a complete proposed spec even from a partial edit.
Parameters
Subtype to propose a change for.
New description, if changing it.
Replacement sample payloads.
New JSON Schema, if changing it.
New mapping spec, if changing it.
Returns
SchemaRegistrationResult
Id of the (possibly reused) registration.
The edited subtype.
Version this edit proposes.
“full_spec” once both a schema and a mapping are known (yours, or inherited from the active version), else “assisted”.
“pending_review”.
Dry-run result, populated when submission_mode is full_spec and examples are present.
Raises
| Exception | When |
|---|---|
AuthError | HTTP 401 or 403 — invalid API key or insufficient OAuth scope for this endpoint. |
ValidationError | HTTP 400, 404, or 422 — malformed JSON, unknown patient, or validation failure (message includes response excerpt). |
ServerError | HTTP 409 (e.g. conflicting external identifier) or repeated 5xx after retries; includes status_code when applicable. |
RateLimitError | HTTP 429 — rate limited; check retry_after (seconds). |
NetworkError | Connection timeout, DNS failure, or read error after retries. |
Previous
deprecate_schemaDeprecates a materialized version (default: the active one), or withdraws a still-pending request if nothing has been materialized yet.
Next

