LMS API Overview
Summary
Source-backed Draft reference for LMS API Overview across the implemented Training Service and, where applicable, Gateway surface.
Audience
API consumers, engineering, QA, support, architecture, security, product, and implementation reviewers.
Reference Content
Architecture
Training Service runs ASP.NET Core 8 and maps minimal API delegates directly to the EF context, domain records, outbox helpers, and a typed Document client. There are no MVC controllers or application command/query handlers in the request path.
Route families
Native discovery and health routes sit at service root. Forty-five LMS operations share one Training route group and cover catalog, paths, enrollments, assessments, certificates, sessions, reports, import/export, evidence, and diagnostics. Gateway exposes a read-only training proxy and includes training data in its ESS dashboard.
Response and maturity
Success responses use direct DTOs, anonymous objects, entity collections, CSV/binary files, or the shared service-info envelope. Validation failures and explicit not-found/conflict branches use message objects. This is not a uniform envelope and ProblemDetails is not configured.
The implementation is Transitional. It has substantial working breadth and smoke coverage, but security policy, ownership, pagination, API versioning, and several lifecycle controls remain Foundation or Not implemented.
Source References
microservices/src/training-service/training-service.csprojmicroservices/src/training-service/Program.csmicroservices/src/training-service/Api/TrainingEndpoints.csmicroservices/src/gateway-api/EssEndpoints.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