HTTP API Reference¶

Each deployed service owns an OpenAPI document at 'services//openapi.yaml'. The API Gateway document defines its operational endpoints and summarizes routed public prefixes; each routed operation remains in the owning service document. Service documents also include internal endpoints used by the gateway or another service. The interactive views below are read-only renderings of those source files.

Authentication requirements are declared per operation. Anonymous routes may accept a Visitor ID; account and brand routes require a Keycloak-issued token at the gateway, which derives trusted identity headers. Internal service endpoints are not public interfaces.

Redocly linting validates the documents, and MkDocs renders them. The repository does not generate clients from these specifications or run a complete handler-conformance test. Handler/router tests and the container journey provide partial runtime evidence.

Service contracts¶