What is xAPI?
xAPI is the standard that followed SCORM, recording learning events in more detail and outside a single course player. Each event is expressed as a statement with an actor and a verb applied to an object, stored in a learning record store. Because a statement can originate in any system, the record extends to activity that never happened inside a course.
Also called: Experience API, Tin Can API
Why the audit question lives outside the course player
The case for xAPI is rarely about richer analytics. An audit question is usually about something a course player cannot see, such as whether a person who completed a module then performed the task correctly in the operational system. SCORM records that a course was completed with a score attached, and that is the limit of what it can tell anyone. xAPI makes the wider record possible and transfers the work to whoever has to decide which statements are worth keeping.
- Statements can originate in an operational system as well as in a course.
- A record store holds evidence a learning platform was never designed to carry.
- Granular statements let a question about one person's activity be answered precisely.
- Freedom in the statement vocabulary creates a governance obligation to define it.
How xAPI works
- A statement vocabulary is agreed so every system describes an event the same way.
- Each system emitting statements is registered against the record store with credentials.
- Modules emit statements at the points that carry evidentiary value.
- Statements are stored immutably with their timestamp and their source.
- Reporting queries the record store rather than a course level completion flag.
- Retention and access are governed, since statements accumulate personal data quickly.
How xAPI is evaluated
An xAPI deployment is assessed on whether the statements collected answer the questions actually asked of the record. Examine the following on the live record store:
- share of statements conforming to the agreed vocabulary
- completeness of statements from each registered source system
- query time for a single learner's full history
- storage growth against the retention policy
- proportion of audit questions answerable from statements alone
Limitations, risks and common failure modes
- Vocabulary is left open, so two systems describe the same event differently.
- Statement volume grows faster than the governance around it.
- Personal data accumulates in a record store with no retention rule applied.
- Teams adopt xAPI and continue reporting the same completion flag as before.