Expense API Response and Error Model

Summary

Application results map consistently to HTTP outcomes:

Audience

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

Reference Content

Application results map consistently to HTTP outcomes:

Application outcome	HTTP meaning
Success	Successful response; creation operations use Created
Validation	Bad request
Not found	Resource not found
Conflict	State/integration conflict
Forbidden	Caller not permitted by an implemented application rule

Direct detail reads also return not-found results. Receipt dependency unavailability is represented as service unavailable rather than silently accepting content. Unexpected failures retain framework behavior and must not be inferred as a domain result.

Error bodies expose a message field. No universal problem-details contract, error code catalog, validation-field collection, or concurrency token is confirmed.

Source References

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

Related Articles

• Expense technical documentation
• Expense business documentation

See Also

• Expense module

Keywords

• Expense API
• Response and Error Model

Revision Information

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