API reference¶
Interactive documentation for the scan-bridge HTTP API, rendered from
components/scan-bridge/api/openapi.yaml.
That is the same file a code generator or an openapi-spec-validator
run would use. It is grounded against the actually implemented
handlers in internal/api/, not the aspirational surface once
sketched in CONTAINER_SUITE.md §4.4. Three details worth knowing
before you read it, all called out again at the top of the spec
itself:
GET /profiles/{name}returns capitalized field names (Name,Resolution, ...) — the Go struct behind it only carriesyamltags, soencoding/jsonfalls back to the field names verbatim. Everywhere else in this API the wire format issnake_case.GET /readyhas a real200/503contract as of Phase 1.2h.GET /jobs,GET /jobs/{id}andPOST /jobs/{id}/cancelare real501 Not Implementedstubs — there is no job store yet.
Rendered by Scalar, self-hosted
like everything else on this site — see No third-party
requests for why
proxyUrl and withDefaultFonts are set to disable Scalar's two
default calls to proxy.scalar.com and fonts.scalar.com.