Tech docs — REST reference
This reference is generated, not written: it comes from the same address space, field limits and refusal catalog the running server publishes through OPTIONS. It cannot describe a control the server does not actually serve, and it cannot miss one either.
Before you read a row
Every address answers GET. One that takes a write below answers PATCH too, and OPTIONS always publishes the live contract — the writable fields, the ranges and the enumerated options — for whichever is true on the server you are talking to.
Add it to a GET and it becomes a server-sent event stream emitting exactly what that GET returns, snapshot first. A handful of rows — marked on demand below — only compute while at least one client is watching them.
Built from an OpenMixer checkout's travel-sheet.json, engine-ui-rows.json and message-code.ts — 188 rows across 37 families, generated 2026-09-02.
By family
/docs/rest/refusal-codes
Every refusal, warning and undo-entry label the server can send, with the parameters each one carries. Nothing below the surface renders display prose directly — a code plus its parameters travels the wire, and the client's own locale supplies the sentence.
/openapi.json
The same 188 rows and the refusal catalog as one standard, tool-readable document — paths, request and response JSON Schema, and the refusal codes as reusable components. Generated, not hand-written, same as everything else on this page.
