Learning (LMS) - Bindbee Docs

Everything under https://api.bindbee.dev/api/lms/v1/. Seven models answering two questions: what training exists, and who has done it.

The models

Group	Models	What it answers
People	Users	Who the learners are
Content	Courses, Contents, Skills, Categories	What training exists
Progress	Completions, Enrollments	Who was assigned it, and who finished

An enrollment is not a completion. An enrollment means the training was assigned, which is exactly what someone out of compliance also has. Mandatory training reporting needs completions, and the gap between the two is the report - see LMS models.

An LMS user is a separate identity from an HRIS employee, even when it is the same person. There is no automatic link between them; matching the two is your application’s job.

Read-only

The LMS category has no write endpoints. Training records are created in the learning platform, and Bindbee reads them. Where a write is genuinely required, Passthrough reaches the source system’s own API directly - at the cost of a provider-specific request and response shape you maintain yourself.

Coverage varies more than elsewhere

Skills in particular are unsupported by many LMS platforms, and the model will be empty for those integrations. Contents may be sparse where a system does not distinguish material within a course. Check against the integrations your customers actually use rather than assuming the full model set is populated - see Scope & permissions.

Where to start

LMS models

Assignment versus achievement, and the catalog.

Pagination

Every collection endpoint works this way.