LMS Course API

Summary

Source-backed Draft reference for LMS Course 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

Operations

Method and route	Behavior	Success	Confirmed failures
GET course collection	Tenant-filtered ordered list	200 Course DTO collection	No explicit branch
POST course collection	Creates Draft course with nested content	201 Course DTO	400 value/tenant validation; persistence conflicts possible
POST publish action	Sets Published and publish time	200 Course DTO	404
POST archive action	Sets Archived and archive time	200 Course DTO	404

Exact route strings and contracts appear in the endpoint catalog.

Publish and archive assign status directly; no source guard restricts the prior state, module completeness, trainer, category, or duration beyond value-object validation. Repeated publish preserves the first publication time; repeated archive refreshes the archive time. Create writes audit and timeline evidence, while publish/archive also write evidence. Assignment requires Published status.

No course detail, update, delete, dedicated catalog, search, filter, paging, or trainer-assignment endpoint exists. Category is optional data, not a governed taxonomy.

Source References

• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Domain/TrainingEntities.cs
• microservices/src/training-service/Domain/TrainingEntities.cs

Related Articles

• LMS API documentation
• LMS technical documentation

See Also

• Endpoint catalog
• API limitations

Keywords

• LMS API
• Training Service
• Source-backed contract

Revision Information

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