Operations
Get OpenAPI JSON
Download the OpenAPI 3.1 specification for this API converted to JSON.
GET
This OpenAPI document (JSON)
Serves the same OpenAPI 3.1 document as
Get OpenAPI YAML, converted from
the embedded YAML to JSON once at process start. Use it with tooling that
expects JSON — code generators, request validators, API gateways. The
content is identical to the YAML form; only the encoding differs. No
authentication is required.
The conversion decodes the YAML into a generic map and re-encodes it with
Go’s
json.Marshal, so the body is a single compact line with object keys
in alphabetical order (components, info, openapi, paths,
security, servers, tags) rather than the authored order. Pipe it
through jq . if you want to read it.
Example Request
Response
Content-Type: application/json. The body is the specification document
itself — a bare OpenAPI object, not a data envelope. The excerpt below is
pretty-printed and abridged (info.description, info.license, tags,
every path but /health, the /health response content and 503, the
portalSession and sessionCookie security schemes, and all of
components.parameters, components.responses and components.schemas
are omitted); the key order matches the real body, and every value shown
is verbatim.
Errors
This endpoint has no failure modes of its own and always returns200. The
YAML-to-JSON conversion happens at boot and a conversion failure aborts
startup, so a running instance never serves a malformed document.Authorizations
Response
200 - application/json
The OpenAPI 3.1 specification in JSON.
The response is of type object.