Skip to main content

Attendance API Response and Error Model

Summary

Direct, compatibility, and foundation surfaces intentionally use different response conventions.

Audience

Frontend and backend developers, QA and support engineers, and implementation partners.

Reference Content

Source outcomeDirect responseCompatibility response
Success200 with ApiResponse<T>: success, message, data, optional correlationId, optional errorsUsually 200 with bare DTO, array, string, or compatibility object
Validation / domain / argument failure400 failure envelope400 bare error value or text
Missing tenant400 failure envelope with tenant error category400 bare text
Not found404 failure envelope404 bare error value
Conflict409 failure envelopeCompatibility translation generally returns 400
Forbidden application result403 failure envelope403 bare error value or empty body depending on family
Payroll period locked403 through reopen approval result403 bare error value
Authentication challengeRequires deployment-level confirmationRequires deployment-level confirmation
Unhandled failureFramework-level failure; public body is not specifiedFramework-level failure; public body is not specified
External dependency unavailableNo distinct public status is confirmedNo distinct public status is confirmed

The API does not implement RFC Problem Details as its documented contract. Direct success example: {"success":true,"message":"Success","data":[],"correlationId":"example-correlation"}. Direct error example: {"success":false,"message":"Request failed.","data":null}. Compatibility examples are documented per family because shapes vary.

Source References

  • microservices/src/attendance-service/Api/AttendanceDirectEndpoints.cs
  • microservices/src/attendance-service/Api/AttendanceCompatibilityEndpoints.cs
  • microservices/src/attendance-service/Application/Common/Cqrs.cs
  • microservices/src/contracts/Common/ApiResponse.cs
  • microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs

See Also

Keywords

  • Attendance API
  • Attendance API Response and Error Model

Revision Information

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