xAPI — Experience API

The statement-based learning records standard that extends tracking beyond the LMS — mobile learning, simulations, serious games, real-world activities, and more.

History

To extend the concepts of SCORM to track performance data on emerging learning capabilities (e.g., mobile learning), DoDI 1322.26 was updated to allow a more capable standard called the Experience API, or xAPI. Unlike SCORM, xAPI can be used to track and share data from mobile learning, simulations, virtual worlds, serious games, real-world activities, wearable devices, experiential learning, social learning, offline learning, and more.

  • 2011–2013 — Developed as IEEE P9274.1.1, building on the LETSI Federation’s 100+ white papers.
  • 2013 — xAPI v1.0.1 released (October 2013).
  • 2019 — xAPI v1.0.3 released, the most widely deployed version.
  • 2024 — xAPI v2.0 released, adding JSON-LD, activity states, and modernized data structures.

LRS endpoints

An xAPI Learning Record Store (LRS) exposes six REST endpoints for reading and writing statements:

  • GET /statements — Query statements with a rich filter language (agent, verb, activity, registration, since/until, etc.).
  • POST /statements — Create one or more statements.
  • GET /statements/{id} — Retrieve a single statement by ID.
  • PUT /statements/{id} — Update a statement (e.g., attach an annotation).
  • DELETE /statements/{id} — Delete a statement.
  • GET /activities/state/{id} — Read and write activity state (v2.0).

Specifications & resources

Ecosystem

xAPI Profiles define how xAPI is applied to specific domains. The ADL Initiative maintained guidance for profile servers and profile development:

On lms.technology