Someone in a meeting says the team should "move to xAPI", and heads nod. Then the follow-up questions start. Do we need new software? Is the LMS enough? What is a Learning Record Store, and who has to run it? The xAPI and learning record store conversation tends to go in circles because the terms arrive before the definitions. What is xAPI, what does a Learning Record Store actually do, and do you need one at all?

xAPI is a standard for sending records of learning activity, called statements, to a Learning Record Store (LRS), which is a server that receives, validates, stores and returns those statements. Each statement follows an actor, verb, object pattern: a person did something to something. Statements can come from courses, simulations, apps or offline activities, so xAPI can track learning that never happens inside an LMS. You need an LRS whenever you use xAPI, though some LMS platforms include one. If you only need to know whether people finished and passed courses launched from your LMS, SCORM is often still enough.

What Is xAPI in Plain Terms?

xAPI, the Experience API (originally known as Tin Can), is a specification for describing learning experiences as short structured records and sending them over the web. The Advanced Distributed Learning (ADL) Initiative describes the Experience API as a data and interface standard that lets software capture and share data on human performance.

What Is xAPI and Do You Need a Learning Record Store? – Statements, LRS Basics and When SCORM Is Enough - 3D Wireframe Animation

The useful comparison is with SCORM. SCORM assumes a course launched inside an LMS, talking to it through a browser-based API, with a fixed list of data fields. xAPI removes those assumptions. Any system that can make a web request can send a statement, and the statement can describe almost any activity: completing a module, attempting a simulation step, reading a procedure on a phone, attending a workshop.

The standard has also changed hands over time. The xAPI overview notes that it is an IEEE approved standard, IEEE 9274.1.1-2023, which gives it a formal home beyond the original ADL project.

That freedom is both the strength and the cost. SCORM tells you exactly what to record. xAPI asks you to decide.

What Does an xAPI Statement Look Like?

An xAPI statement is a small JSON document built around three parts: actor, verb and object. The xAPI overview describes this as an "I did this" pattern. Here is a simplified made-up example of a learner passing a quiz:

{
  "actor": {
    "objectType": "Agent",
    "account": {
      "homePage": "https://lms.example.com",
      "name": "learner-1042"
    }
  },
  "verb": {
    "id": "http://adlnet.gov/expapi/verbs/passed",
    "display": { "en-US": "passed" }
  },
  "object": {
    "id": "https://example.com/courses/forklift-safety/final-quiz",
    "definition": { "name": { "en-US": "Forklift Safety Final Quiz" } }
  },
  "result": {
    "score": { "scaled": 0.85 },
    "success": true,
    "completion": true,
    "duration": "PT14M30S"
  },
  "timestamp": "2025-03-04T10:15:00Z"
}

Reading it piece by piece:

  • The actor identifies the learner. Here it uses an account on a named system; other identifiers are allowed.
  • The verb has an id, a web address that acts as a unique name, plus a display label for people.
  • The object is the activity, also identified by a unique address.
  • The result holds the score, success, completion and duration, much like SCORM's fields.
  • Optional context can link the statement to a parent course, a registration or an instructor.

Agreeing on verbs and activity IDs across a team is the part that takes real work. Two courses that both mean "finished" but use different verbs will not line up in a report.

xAPI and Learning Record Store Basics: What Does an LRS Do?

A Learning Record Store is the server that xAPI statements are sent to. ADL describes it as a server that receives, validates, stores and provides access to xAPI statements. Without one, statements have nowhere to go.

In practice an LRS does four jobs:

  1. Accepts statements from authorized sources over a defined web interface.
  2. Checks that each statement is valid before storing it.
  3. Stores statements without changing them. Statements are not edited after the fact; a wrong statement is cancelled by a separate "voiding" statement.
  4. Returns statements to authorized tools that query by learner, verb, activity or time range.

To send statements, a course or app needs two things: the LRS endpoint (the web address that accepts statements) and credentials that prove it is allowed to write there. How those reach the course matters. Credentials hard-coded into a package that anyone can download are effectively public, so a learner, or anyone else, could post statements to your LRS. Launch methods that hand the course a short-lived credential at launch time avoid that problem, which is one more argument for a defined launch process.

An LRS also offers storage for course state, so an xAPI course can save a bookmark or progress data much as a SCORM course uses suspend data. Some LRS products add dashboards and reports on top. Others are deliberately plain and expect you to connect a reporting tool.

Can an LMS Act as a Learning Record Store?

Sometimes. The xAPI overview notes that an LRS can sit inside an LMS or stand on its own, and many LMS products advertise built-in xAPI support. "Supports xAPI" can mean very different things, though, so ask specific questions:

  • Does the LMS store every statement a course sends, or only the ones it uses for completion?
  • Can other systems, such as a simulator or a mobile app, send statements to it?
  • Can you query or export the raw statements?
  • Can it forward statements to another LRS?
  • How does it launch xAPI courses and pass learner identity to them?

The last question matters more than it looks. Plain xAPI does not define how an LMS should launch a course, so different systems solved it differently. That gap is the main reason cmi5 exists: it adds launch, authentication and reporting rules on top of xAPI for LMS-launched content.

When Is SCORM Still Enough?

More often than the enthusiasm suggests. The honest comparison of xAPI vs SCORM starts with what you need to know. SCORM is usually enough when:

  • Every course is launched from the LMS.
  • Reports only need completion, pass or fail, score and time.
  • Nobody plans to analyze answers or behaviour in detail.
  • Your LMS handles SCORM reliably and your reports are built around it.

xAPI starts to earn its place when any of these apply: learning happens outside the LMS, you want detail on decisions inside a scenario or simulation, you need to combine data from several systems, or learners work offline and sync later. If none of them applies, switching standards adds setup and decisions without adding answers.

What Should You Track With xAPI, and What Should You Skip?

Track what answers a question someone has actually asked. Skip the rest. An LRS will happily accept a statement for every click, and the result is a large pile of data nobody reads.

Picture a made-up case. Say a sales team wants to know why new staff struggle with pricing objections. A scenario course could send a statement each time a learner chooses a response at the three key decision points, with the choice recorded in the result. That is a handful of statements per learner, and it answers the question directly. Tracking every slide view in the same course would add many more statements and answer nothing new.

A short planning list helps:

  1. Write down the questions the data must answer.
  2. List the activities and moments that produce that evidence.
  3. Choose verbs from a shared vocabulary or published profile, not invented ones.
  4. Agree on activity IDs before anyone builds anything.
  5. Decide who may read the data and for how long it is kept.

The last step is not only technical. xAPI statements describe identifiable people, so involve your privacy or data protection team early. They can say what your organization's policies and the laws that apply to you require.

xAPI Earns Its Keep When You Have Questions SCORM Can't Answer

xAPI and a learning record store work as a pair: statements describe what people did, and the LRS keeps them and hands them back on request. Together they can track learning in places an LMS never sees, at a level of detail SCORM was never designed for.

That capability only pays off with a purpose behind it. Start from the questions, choose a small shared set of verbs and activities, confirm what your LMS or LRS really stores, and keep SCORM where it already does the job. A modest, well-planned set of statements beats an enormous log of clicks every time someone opens a report.