xAPI and learning records in OSH

xAPI communicates learning experiences through structured records. Its usefulness depends on consistently defining events, identity and evidence.

In brief

xAPI communicates learning experiences through structured records. Its usefulness depends on consistently defining events, identity and evidence.

Contents
  1. What Experience API provides
  2. Events with agreed meaning
  3. Application to preventive experiences
  4. Identity and data protection
  5. Design example
  6. Difference from an LMS
  7. Related concepts
  8. References

A–Z dictionary →

What Experience API provides

Experience API, or xAPI, enables information about learning activities and experiences to be communicated between technologies. It uses structured statements describing who performed an action and on which activity. These statements are stored in a Learning Record Store, or LRS. The standard facilitates exchange but does not itself decide what it means to learn or be competent for a job.

Events with agreed meaning

Recording that someone opened, completed or passed an activity requires each event to be defined. Two systems may use similar words with different rules. Identifiers, vocabulary and context should therefore be agreed before comparing results. The model must distinguish a visit, an attempt and an assessed demonstration, preventing reports from adding together fundamentally different events.

Application to preventive experiences

A project can bring together evidence from courses, simulations or digitised practice, provided the tools are prepared to emit appropriate records. Evaluation of training effectiveness needs to interpret these data alongside the preventive objective. The volume of events collected does not equal a reliable measure of learning.

Identity and data protection

Each activity must be correctly linked to its participant without collecting unnecessary information. Recipients, permissions, retention and error handling are also defined. Learning records may reveal individual behaviour or results and are not considered public by default. An LRS is a technical component within a process that has management responsibilities.

Design example

In a hypothetical example, a simulation records an attempt and its result while the LMS retains course completion. How to link them without counting the same evidence twice is agreed. Testing includes retrying, connection errors and later receipt, checking that final statuses make sense to both the training manager and participant.

Difference from an LMS

An LRS stores statements and allows them to be queried; a learning platform may also organise enrolment, content and communication. Functions depend on each implementation. Adopting xAPI does not automatically replace the LMS or turn an unchanged SCORM course into an xAPI experience. Versions, profiles and end-to-end integration must be checked.

References

  1. ADL: xAPI data model. Official source
  2. ADL: xAPI Wrapper and statements. Official source

Editorial information

Publication date: 1 November 2026.

Editorial responsibility: Sabentis Editorial Team.

Author: Pablo RodríguezLinkedIn

Executive Vice President of the ORP International Foundation and Chief Financial Officer of Sabentis.

Request a Demo

Discover all that Sabentis can do for your organization.

Try Sabentis

request a demo
stars 5
GetApp Software Advice Capterra