API overview.

Everything the Radial UI shows comes through an API you can call yourself: a versioned REST surface under /api/v1.0, described by a published, spec-validated OpenAPI contract.

The contract is the product

The OpenAPI document is treated as a deliverable, not an afterthought: it validates clean, every operation has a stable operationId, pagination is documented once and used consistently, and errors return documented JSON shapes. If you build against the spec, the spec is telling you the truth.

Authentication

Access is token-based: a personal access token, created in Radial, is exchanged for a short-lived session token that authenticates API calls — one pattern for a script, a notebook, or an integrated product.

What the surface covers

Resources map to the concepts in these docs: cases and case search, protocols, structure dictionaries and their dose-endpoint definitions in Mayo syntax, DICOM operations (staged studies, imports, query and retrieve, job status), and module listings for segmentation and radiomics. A few representative operations:

Where the contract is in its life

Honest framing: the contract is young, and that is the opportunity. There is no legacy integration burden — a design partner building against Radial today co-shapes the surface with us while breaking changes are still cheap, instead of inheriting decisions made for someone else.