Documentation

HTTP APIs (OpenAPI)

The OpenAPI contracts of krizaka-users, krizaka-billing and krizaka-notifications.

Each domain service will publish the OpenAPI document of its HTTP surface in its *-api jar (META-INF/openapi/), and this page will render it — operations, parameters, request and response schemas — with Fumadocs OpenAPI, so the documentation of a contract is the contract itself.

What every API already shares

  • Errors are application/problem+json with a stable code and the requestId — see Web and Problem Details.
  • Authentication is a bearer session token verified locally; /internal/v1/** takes a SERVICE token — see Security.
  • Lists page by key with an opaque cursor and return nextCursor until the last page.

On this page