Skip to main content

Expense OpenAPI and Discovery

Summary​

The service registers endpoint discovery and Swagger/OpenAPI generation and maps a service-information surface plus process health. Named native operations improve discovery; compatibility operations are grouped separately.

Audience​

API consumers, backend and frontend developers, QA, architects, implementation partners, and support.

Reference Content​

The service registers endpoint discovery and Swagger/OpenAPI generation and maps a service-information surface plus process health. Named native operations improve discovery; compatibility operations are grouped separately.

Generated OpenAPI reflects Minimal API signatures but does not prove authorization, tenant safety, workflow availability, Document availability, Payroll readiness, or business policy. Consumers must pair the generated contract with this documentation and the Technical/Business sections.

Versioned API documents, formal compatibility-version headers, deprecation metadata, and a published client SDK are not confirmed.

Source References​

  • microservices/src/expense-service/Program.cs
  • microservices/src/expense-service/Api/ExpenseEndpoints.cs

See Also​

Keywords​

  • Expense API
  • OpenAPI and Discovery

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly