Attendance Employee Profiles API
Summary
Three direct operations expose the active Attendance roster and upsert the local employee-profile projection. This is not Employee master-data ownership.
Audience
Backend/frontend developers, Employee integration engineers, QA engineers, architects, and implementation partners.
Reference Content
Authentication: Bearer context expected; administrative/integration authorization requires confirmation. Tenant: required for upsert and expected for tenant-filtered reads. Maturity: Direct/Shadow, Transitional projection.
| Operation | Method and public route | Contract | Responses and behavior | Safe example |
|---|---|---|---|---|
| Attendance roster | GET /attendance/employees | No parameters/body | 200 ApiResponse<AttendanceEmployeeDto[]>; active profiles, read-only | GET /attendance/employees → data:[]; failure body follows direct model where handled. |
| Upsert local profile | PUT /attendance/employee-profiles | EmployeeProfileUpsertRequest | 200 ApiResponse<int>; 400 invalid; inserts/updates projection and audit, no attendance event | Fictional body with laborId:4242, name:"Example Employee", isActive:true, attendanceMode:"Direct"; success returns fictional id; missing employee/name → 400. |
| Profile roster alias | GET /attendance/employee-profiles | No parameters/body | 200 ApiResponse<AttendanceEmployeeDto[]>; same active projection query | GET …/employee-profiles → data:[]; handled tenant failure where raised → 400. |
Upsert fields are laborId, name, optional employee code/contact/organization/manager context, optional joining date, isActive, standardDailyHours, attendanceMode, half-day/absence threshold fields, and optional legacy shift name/start/end context. Name and positive employee reference are required. Blank attendance mode falls back to Direct in the application service. Customer-specific numeric values are intentionally omitted from examples.
Response roster fields include identity/display and contact/organization context, joining date, mode, standard/threshold context, tenant reference, and active state. Consumers must apply data minimization. There is no get-by-id, delete, patch, or confirmed event-driven synchronization endpoint. Employee Service remains the system of record.
Source References
microservices/src/attendance-service/Api/AttendanceDirectEndpoints.csmicroservices/src/attendance-service/Application/Dtos.csmicroservices/src/attendance-service/Application/Services/EmployeeProfileService.csmicroservices/src/attendance-service/Application/Services/AttendanceQueries.cs
Related Articles
See Also
Keywords
- Attendance API
- Attendance Employee Profiles API
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly