Leave Timeline API

Summary

One Direct query returns recent Leave timeline entries, optionally restricted to an employee reference.

Audience

Frontend/backend developers, QA, support, and architects.

Reference Content

Maturity: Direct. Authentication: expected. Authorization: diagnostic/employee scope Requires confirmation. Tenant: tenant-filtered query.

Operation	Method/route	Parameters	Response/status	Behavior
Query Leave timeline	GET /leave/timeline	Optional query laborId	200 LeaveTimelineDto[]	Newest first, maximum 500; read-only; no audit/event/side effects.

Response fields: id, laborId, nullable leaveRequestId, entryType, optional detail, actor, and occurredOn.

Example: GET /leave/timeline?laborId=900001 → 200 [] when no visible entries exist. Actor/detail fields can contain operational or user-derived information and must be redacted before support sharing. No pagination token, date filter, type filter, or get-by-id exists.

Source References

• microservices/src/leave-service/Api/LeaveEndpoints.cs
• microservices/src/leave-service/Application/Dtos.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs

Related Articles

• Leave API
• Authentication and context
• Response and error model

See Also

• Leave technical documentation
• Leave business documentation

Keywords

• Leave API
• Leave Timeline API
• Endpoint reference

Revision Information

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