Skip to main content

Payroll Input Projection APIs

Summary​

Two foundation queries expose Payroll-owned Attendance and Leave monthly projections for verification.

Audience​

Frontend and backend developers, QA and support engineers, architects, security reviewers, and implementation partners.

Reference Content​

Authentication: bearer context is expected for business APIs; service-local enforcement Requires confirmation. Authorization: no endpoint-specific Payroll Service role policy is confirmed. Maturity: Foundation / Shadow.

OperationMethod and public routePurposeAuthenticationTenant contextRequest typeResponse typeSuccessMaturitySource path
List Attendance projectionsGET /payroll/attendance-snapshotsInspect Payroll-local Attendance inputs.Bearer context expected; service-local enforcement Requires confirmationForwarded or explicit tenant context; exact missing-context mapping Requires confirmationQuery parametersAttendancePayrollSnapshot[]200Foundationmicroservices/src/payroll-service/Api/PayrollFoundationEndpoints.cs
List Leave projectionsGET /payroll/leave-snapshotsInspect Payroll-local Leave inputs.Bearer context expected; service-local enforcement Requires confirmationForwarded or explicit tenant context; exact missing-context mapping Requires confirmationQuery parametersLeavePayrollSnapshot[]200Foundationmicroservices/src/payroll-service/Api/PayrollFoundationEndpoints.cs

List Attendance projections​

  • API family / maturity: Payroll Input Projection APIs; Foundation
  • Authentication / authorization: Bearer context expected; service-local enforcement Requires confirmation. No endpoint-specific role policy is confirmed.
  • Tenant context: Forwarded or explicit tenant context; exact missing-context mapping Requires confirmation.
  • Route parameters: None.
  • Query parameters: Optional tenantId, month, year, legacyEmployeeId.
  • Request body / type: None; Query parameters.
  • Validation: Only checks stated in the error mapping below are confirmed; model-binding failures are framework behavior and not specified as a stable contract.
  • Response body / type: AttendancePayrollSnapshot[].
  • Success / error responses: 200; No endpoint-specific error response is mapped.
  • Business behavior: Inspect Payroll-local Attendance inputs.
  • State and input implications: Read-only. No input projection changes.
  • Audit and event implications: No audit side effect confirmed. No event produced.
  • Compatibility notes: Native Payroll contract.
  • Safe example: GET /payroll/attendance-snapshots?month=7&year=2026 → 200 []
  • Example error: No stable endpoint-specific error example is confirmed.

List Leave projections​

  • API family / maturity: Payroll Input Projection APIs; Foundation
  • Authentication / authorization: Bearer context expected; service-local enforcement Requires confirmation. No endpoint-specific role policy is confirmed.
  • Tenant context: Forwarded or explicit tenant context; exact missing-context mapping Requires confirmation.
  • Route parameters: None.
  • Query parameters: Optional tenantId, month, year, legacyEmployeeId.
  • Request body / type: None; Query parameters.
  • Validation: Only checks stated in the error mapping below are confirmed; model-binding failures are framework behavior and not specified as a stable contract.
  • Response body / type: LeavePayrollSnapshot[].
  • Success / error responses: 200; No endpoint-specific error response is mapped.
  • Business behavior: Inspect Payroll-local Leave inputs.
  • State and input implications: Read-only. No input projection changes.
  • Audit and event implications: No audit side effect confirmed. No event produced.
  • Compatibility notes: Native Payroll contract.
  • Safe example: GET /payroll/leave-snapshots?month=7&year=2026 → 200 []
  • Example error: No stable endpoint-specific error example is confirmed.

Family-level findings​

These endpoints are read-only and do not approve, recalculate, or correct upstream records. Response categories include monthly paid-unit/hour totals and synchronization metadata; employee identifiers and breakdown payloads are intentionally excluded from examples. Access scope requires confirmation.

Source References​

  • microservices/src/payroll-service/Api/PayrollFoundationEndpoints.cs
  • microservices/src/payroll-service/Domain/PayrollEntities.cs

See Also​

Keywords​

  • Payroll API
  • Payroll Input Projection APIs

Revision Information​

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