Skip to main content

Expense API Compatibility and Routing

Summary​

The gateway conditionally transfers only the Expense compatibility slice from legacy owners to Expense Service and also supports a shadow/direct diagnostic surface. Compatibility ownership includes Expense HR-operations mutations, the shared workspace response, and approved-expense aggregation for Payroll clients.

Audience​

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

Reference Content​

The gateway conditionally transfers only the Expense compatibility slice from legacy owners to Expense Service and also supports a shadow/direct diagnostic surface. Compatibility ownership includes Expense HR-operations mutations, the shared workspace response, and approved-expense aggregation for Payroll clients.

Routing is Transitional. When cutover ownership changes, native data writes, audit/timeline evidence, outbox records, and downstream projections are not reversed automatically. Compatibility contracts use legacy numeric identity and shapes while native contracts use typed identity.

Exact deployment toggles, destinations, internal topology, and rollback commands are intentionally excluded. Authentication and tenant context are expected to be forwarded, but enforcement parity requires confirmation.

Source References​

  • microservices/src/gateway-api/Program.cs
  • microservices/src/expense-service/Api/ExpenseCompatEndpoints.cs

See Also​

Keywords​

  • Expense API
  • Compatibility and Routing

Revision Information​

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