What Is xAPI? A Plain-English Guide for IDs (2026)
xAPI explained in plain English — what it tracks, how it differs from SCORM, when to use it, and how cmi5 bridges the two. For instructional designers in 2026.
xAPI — short for Experience API, originally called Tin Can API — is a tracking standard that captures detailed learning data from any platform, not just an LMS. Released as version 1.0 in April 2013 and updated to version 2.0 (formally IEEE 9274.1.1-2023) in October 2023, it's the standard most modern enterprise L&D teams are moving toward when SCORM stops being enough.
This guide explains what xAPI actually does, how it differs from SCORM, when to use each, and what cmi5 is doing in between. Written for instructional designers and L&D professionals who need to make a decision — not technologists implementing the spec.
Quick comparison: xAPI vs SCORM
| SCORM | xAPI | |
|---|---|---|
| Released | 2000 (1.2), 2004 | 2013 (v1.0), 2023 (v2.0) |
| Where it works | Inside an LMS only | Anywhere — LMS, mobile app, simulator, real world |
| What it tracks | Completion, score, time, basic interactions | Anything — every action, every detail, granular |
| How data is stored | In the LMS, tied to one course session | In a Learning Record Store (LRS), independent of any single tool |
| Data format | Limited to predefined SCORM data model | JSON statements: Actor + Verb + Object |
| Best for | Standard compliance courses, LMS-based delivery | Detailed analytics, learning across platforms, mobile/informal/blended |
What does xAPI actually do?
SCORM was built for a world where learning happened inside one place — a course, in one LMS. It tracks five or six basic things: did the learner complete it, did they pass, how long did they spend, and a small number of interaction details. That's the limit of what SCORM can see.
xAPI was built for a different world. Learning happens in a course, yes — but also in mobile apps, in YouTube videos, in coaching conversations, in simulations, on the job. xAPI captures all of that, in detail, in a format that can be queried and analysed.
What xAPI tracks isn't just "did they finish the course." It's every meaningful action: every video they paused, every question they got right or wrong, every page they revisited, every time they came back after closing the window, every step in a process they completed correctly. Granular, structured, queryable.
For most compliance training, that level of detail is overkill. For a sales training programme that runs across an LMS, a simulation tool, and field coaching — it's exactly what you need.
How an xAPI statement works
Every xAPI event is captured as a "statement" in a fixed format:
[Actor] [Verb] [Object]
That's it. Three components. A learner did something to or with something.
Concrete example. A learner finishes a knowledge check inside a course:
Sarah completed the quiz "GDPR Module 3 Knowledge Check" with a score of 80%.
In xAPI format, that becomes:
- Actor: Sarah (identified by her email, account, or ID)
- Verb: completed (using a standardised verb URI from the xAPI vocabulary)
- Object: GDPR Module 3 Knowledge Check (with object ID and context)
- Result: 80% score, plus duration, success/fail, and any other context
Each statement is sent as a JSON object to a Learning Record Store. It sits there permanently, alongside every other statement Sarah ever generates — every course, every interaction, every assessment, every coaching session — all queryable, all linked.
That's what makes xAPI different. SCORM tells you Sarah completed her GDPR course. xAPI tells you Sarah completed her GDPR course, but also that she rewatched the data-handling video three times, scored 60% on her first attempt before reattempting and passing, and showed similar reattempt patterns on the previous module. The second story is the one a learning designer can actually act on.
What's a Learning Record Store (LRS)?
The LRS is the database where xAPI statements live. It's the part most people get confused about, because it doesn't have a SCORM equivalent.
In a SCORM world, your LMS tracks course completions and stores them in its own database. SCORM data is essentially baked into the LMS.
In an xAPI world, the data lives in a Learning Record Store — separate from any individual course, any individual LMS, any individual tool. Multiple sources (your LMS, your mobile training app, your simulation tool, your field coaching app) all send statements to the same LRS. The LRS becomes the single source of truth for everything a learner has done across every platform.
Most LMS vendors now offer an LRS as part of their product or as an add-on. There are also standalone LRS providers — Watershed, Veracity Learning, Yet Analytics — focused specifically on cross-platform analytics rather than LMS administration.
If your organisation only uses one LMS for one type of training, you may never need a separate LRS. If learning happens in five different places and you want one view of it all, an LRS is what makes that possible.
xAPI vs SCORM — when to use each
The honest answer: most courses still don't need xAPI.
SCORM does what 80% of learning teams need. It's universally supported. It's understood by every LMS administrator. It works.
Pick xAPI when:
- Learning happens across multiple platforms (LMS + mobile + simulation + field tools)
- You need granular, interaction-level analytics
- You want to track informal learning, on-the-job application, or coaching
- You're building data-driven personalisation or adaptive learning
- You're integrating learning data with a wider analytics platform (e.g. Tableau, Power BI)
Stick with SCORM when:
- You're delivering standard courses through one LMS
- Your reporting needs are completion, score, and time
- Your stakeholders care about pass/fail compliance, not behavioural analytics
- Your LMS doesn't have an LRS and you're not buying one
- You're a freelance ID or small training provider where the LMS-side complexity isn't worth it
For a deeper dive on SCORM specifically — what it is, the difference between SCORM 1.2 and 2004, and how it works inside your LMS — read our SCORM explainer.
cmi5 — the bridge between SCORM and xAPI
cmi5 is one of the more confusing terms in this space, but the idea is simple: it's an xAPI Profile (a defined set of rules for how to use xAPI) that gives you SCORM-style course launch and tracking, with xAPI's data flexibility underneath.
Where SCORM uses JavaScript inside the browser to talk to the LMS — and requires the course content to live on the same domain as the LMS — cmi5 uses a launch URL with query parameters and standard web services. The course can live anywhere; it just needs to be reachable from the LMS.
In practice, cmi5 means:
- Courses can be hosted anywhere — cloud, CDN, separate server — not just inside the LMS
- Mobile delivery is genuinely supported (native apps and mobile web both work)
- You get xAPI-level granular tracking without rebuilding your entire LMS architecture
- Content is launched from the LMS the same way SCORM is, so administrators don't need to relearn anything
cmi5 hasn't been adopted as widely as SCORM yet. Most major LMS platforms support it now, though support varies by version and product tier — check with your specific vendor before committing. If you're shopping for an LMS in 2026, explicit cmi5 support is a real differentiator worth asking about.
How to publish content as xAPI
Most modern authoring tools support xAPI export alongside SCORM:
- Articulate Storyline and Rise 360 — full xAPI support; you choose the format on publish
- Adobe Captivate — xAPI export available, including custom statements via JavaScript
- iSpring Suite — supports xAPI publishing as one of several output formats
- Lectora — strong xAPI support, particularly for compliance and accessibility contexts
- Custom HTML / JavaScript — you can write your own xAPI statements via the xAPI library if you have developer capacity
Our full comparison of elearning authoring tools covers each of these in detail.
A note on Co.llab. Co.llab is the AI-first authoring tool I'm building (full disclosure: Co.llab is built by The Human Co., my company). At launch it supports SCORM 1.2 and SCORM 2004 — the standards that cover the vast majority of current LMS deployments. xAPI export isn't a launch feature. If your team specifically needs xAPI tracking — for cross-platform analytics or detailed behavioural data — Storyline, Rise, Captivate, or iSpring are the established options. If your needs are SCORM-based course delivery with AI doing the production work, Co.llab was built specifically for that. More on what Co.llab does and how it works here.
When xAPI doesn't make sense
Honest framing — xAPI gets oversold in some quarters of the L&D conversation. The fact that a standard can do something doesn't mean your team needs it.
Skip xAPI when:
- Your stakeholders only ask for completion and pass/fail data (xAPI gives you no value here)
- You don't have an LRS, can't afford one, and don't have the appetite to set one up
- Your team doesn't have anyone to interpret the analytics — granular data with no analyst is just noise
- Your LMS doesn't natively support xAPI, and you're not changing LMS soon
- Your courses are simple, single-format, and live inside one LMS
The cost of doing xAPI badly — generating noise without insight — is higher than the cost of sticking with SCORM and being clear about what you're tracking.
The honest bottom line
xAPI is the future. cmi5 is the practical present. SCORM is what most teams are still using and will be for years.
If you're an enterprise L&D team running cross-platform learning, building adaptive systems, or doing serious learning analytics — xAPI matters. Get familiar with it now.
If you're a freelance ID, a small training provider, or a team running standard compliance courses — SCORM is still the right answer for the foreseeable future. xAPI is a tool to know about, not necessarily one to use.
The right standard is the one your LMS supports, your reporting needs justify, and your team can actually use. Anything else is a tool looking for a problem.
Try Co.llab when it launches
Co.llab is in closed beta, launching 18 June 2026. The first 50 purchases at launch get founder pricing — £199 for lifetime ownership of the tool. Standard pricing after that is £299, still one-time payment, no subscription.
Join the beta now and get 130 free AI prompts for instructional designers — a working toolkit you can use today, regardless of whether you end up buying Co.llab at launch.
By Paul Thomas, L&D consultant and founder of The Human Co.