LMS Reports API
Summary
Source-backed Draft reference for LMS Reports API across the implemented Training Service and, where applicable, Gateway surface.
Audience
API consumers, engineering, QA, support, architecture, security, product, and implementation reviewers.
Reference Content
Confirmed endpoints
| Report | Projection | Filtering/paging |
|---|---|---|
| Courses | Lifecycle counts plus enrollment completion ratio | Tenant filter; no request filters or paging |
| Enrollments | Counts by status | Tenant filter; no request filters or paging |
| Assessments | Assessment/attempt outcome aggregates | Tenant filter; no request filters or paging |
| Certificates | Counts by lifecycle and near-expiry window | Tenant filter; no request filters or paging |
| Learning paths | Path, assigned-subject, and completion aggregates | Tenant filter; no request filters or paging |
| Subject summary | Pending, overdue, and simplified mandatory metrics for supplied integer | Path identifier only; no paging |
| Dashboard | Composition of the five aggregate DTOs | No request filters or paging |
The subject-summary route names its path value as a manager reference, but the query treats it as the learning subject. It does not use manager hierarchy. Its mandatory metric treats all Published courses as mandatory because mandatory flags are not modeled. These semantics are explicitly disclosed by the response note.
No session, trainer activity, attendance, configurable mandatory-training, sorting, pagination, or report-specific export endpoint exists. Separate export APIs produce course, enrollment, assessment-result, and certificate CSV files.
Source References
microservices/src/training-service/Api/TrainingEndpoints.csmicroservices/src/training-service/Infrastructure/TrainingDbContext.cs
Related Articles
See Also
Keywords
- LMS API
- Training Service
- Source-backed contract
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly