Key Takeaways
xAPI (Experience API / Tin Can API) is an IEEE-approved standard that records any learning experience, online or offline, across any device, as structured Actor–Verb–Object statements sent to a Learning Record Store.
It was developed from 2011 by ADL and Rustici Software as ‘Project Tin Can,’ released as v1.0 in 2013 and updated to v2.0 in October 2023, addressing SCORM’s core limitations around mobile, offline, and multi-platform tracking.
The LRS (Learning Record Store) is the essential infrastructure piece that receives, stores, and surfaces xAPI data, it is not optional. It can be standalone or embedded in an LMS, and it is what enables a single view of learning across multiple systems.
xAPI is not a SCORM upgrade – it is a different measurement philosophy. SCORM tracks course completion; xAPI tracks the full learning journey including simulations, mobile activity, peer interactions, and real-world tasks.
The clearest ROI cases for xAPI are VR/simulation training, mobile and field-based learning, multi-LMS environments, and programmes where you need to connect learning data to business performance outcomes.
Implementation is significantly more complex and costly than SCORM – it requires LRS infrastructure, technical expertise, and stakeholder buy-in. A pilot-first approach on one high-value programme is the safest entry point.
A hybrid strategy – keeping SCORM for existing compliance content and adding xAPI for new, richer programmes, is the pragmatic path for most mid-sized organisations rather than a full migration.
xAPI, short for Experience API and originally nicknamed Tin Can API – is an IEEE-approved eLearning standard that records learning experiences wherever they happen: inside an LMS, on a mobile device, in a simulation, even offline. It replaces the old assumption that learning only happens in a browser-based course tracked by SCORM. If you are building or rethinking your organisation’s learning ecosystem, understanding xAPI is one of the most practical investments of your time.
This guide covers what xAPI is, how it works, what separates it from SCORM, and critically, when it actually makes sense for your L&D team to use it.
xAPI is a learning data standard that tracks experiences far beyond what SCORM can see
xAPI (Experience API) is an IEEE-approved specification (IEEE 9274.1.1-2023) that collects structured data about virtually any learning experience, formal or informal, online or offline, across any device or platform. Where SCORM could only report on what happened inside an LMS course window, xAPI can record what a learner does in a mobile app, a VR simulation, a conversation with a mentor, or a job-side task.
The standard uses a simple vocabulary: every event is captured as a statement. That statement says who did what, always in the same format and sends it to a central database called a Learning Record Store (LRS). Different systems, different vendors, different geographies, all speaking the same language.
When we started experimenting with xAPI on blended programmes that combined e-learning modules with field-based tasks, the first thing we noticed was how much data we had been missing. Completion rates and quiz scores told us very little about how learners applied skills on the job. xAPI gave us a window into that gap. According to ADL Initiative data, xAPI supports tracking across more than 20 different learning activity types, including simulations, games, mobile apps, and social collaboration.
xAPI is not just a newer version of SCORM – it is a fundamentally different approach to what “learning data” even means.
The origin story of xAPI explains why it was built as a SCORM replacement – and why it is more than that
In 2010, ADL (Advanced Distributed Learning, a US Department of Defense initiative) recognised that SCORM was increasingly inadequate for modern learning. Mobile devices were everywhere, SCORM could not run on smartphones, and cloud-based learning was exploding. ADL issued a Broad Agency Announcement asking for ideas for the next generation of the standard.
They awarded the contract to Rustici Software, a Nashville-based company with deep SCORM expertise. Rustici named the research phase “Project Tin Can” because it was conceived as a two-way conversation with the eLearning industry, like talking through a tin can telephone. The resulting specification was published as version 1.0 in April 2013. In October 2023, xAPI 2.0 was released, bringing significant updates to statement structure and conformance testing.
In our experience working with L&D teams who went through the SCORM era, there is often a misconception that xAPI is just “SCORM but better.” It is more accurate to say that SCORM tells you whether a learner finished a course, while xAPI tells you what a learner actually did across their entire learning journey. That shift in framing is what changes how L&D functions think about measurement.
After understanding what xAPI is, L&D teams need to know how to actually build xAPI-enabled content.
xAPI statements work on a simple Actor–Verb–Object structure that anyone can understand
Every piece of learning data in xAPI is recorded as a statement. Each statement follows an Actor–Verb–Object pattern that mirrors natural language. For example: “Sarah completed the fire safety simulation.” Or: “James scored 90% on the compliance assessment.” Or even: “Priya watched the product demo video for 12 minutes.” These structures allow any learning event to be described consistently.
The Actor is the learner or group. The Verb describes the action, xAPI has a defined library of verbs like ‘completed,’ ‘passed,’ ‘attempted,’ ‘answered,’ and ‘experienced.’ The Object is what the action was performed on: a course, a video, a quiz, a real-world activity. Statements can also carry additional context like scores, timestamps, device type, and duration.
One thing that surprises L&D teams when they first dig into xAPI is how readable the statements are. Because the format is JSON-based and human-readable, you do not need to be a developer to understand what a statement is reporting. When we ran our first xAPI pilot, even the learning designers on the team could look at raw statement logs and make sense of them within a few hours.
Key xAPI statement components include: actor (who), verb (what action), object (what it happened to), result (score, completion, success), context (device, instructor, group), and timestamp.
The Learning Record Store (LRS) is what makes xAPI’s multi-system tracking possible
The LRS – Learning Record Store, is the database that receives, stores, and surfaces xAPI statements. It is the critical infrastructure piece that sits at the centre of any xAPI implementation. Without an LRS, you can generate xAPI statements but have nowhere to send them. Think of it as a universal inbox for all learning data across your organisation.
An LRS can be standalone (a separate product), or it can be embedded inside an LMS. Some modern LMS platforms like Moodle and several enterprise platforms have built-in LRS functionality. Others require you to integrate with a third-party LRS such as Rustici Engine, SCORM Cloud, or Watershed. The LRS receives statements from any xAPI-compliant system, your LMS, a mobile app, a VR platform and consolidates them into one place for reporting and analysis.
The distinction between an LRS and an LMS matters. An LMS manages and delivers learning content. An LRS stores learning records. They serve different functions. According to Rustici Software, the originators of xAPI, an LRS can exist independently or as a component of an LMS, but it is always a required element of any working xAPI ecosystem.
In practice, when we implemented xAPI for a client running compliance training across three different platforms, the LRS was the piece that finally gave them a single view of learner activity. Before that, data lived in three separate systems with no way to connect it. Choosing the right LRS, one that matched their reporting needs without requiring heavy developer resource, took more time than any other decision in the project.
xAPI and SCORM are not the same thing, and understanding the difference matters for your strategy
SCORM and xAPI are both eLearning standards developed under the ADL umbrella, but they solve different problems. SCORM is designed primarily to package and deliver course content to an LMS, tracking a narrow set of data: completion, score, pass/fail, and time spent. xAPI is designed to track any learning experience, across any system, storing rich data in an external LRS. Most organisations need to understand both before deciding which to use, or whether to run both simultaneously.
Here are the most meaningful differences for L&D teams:
- Offline capability: SCORM requires a live internet connection and an active LMS session. xAPI can capture learning data offline and sync it once connectivity is restored.
- Device compatibility: SCORM was never built for smartphones. xAPI works across phones, tablets, medical devices, hardware simulators, and more.
- Data richness: SCORM reports completion and score. xAPI reports almost anything, including decisions made in a simulation, time on specific content sections, or peer interactions.
- System dependency: SCORM content must live inside an LMS. xAPI content can be hosted anywhere, a website, a mobile app, a standalone server.
- Cost and complexity: SCORM is simpler and cheaper to deploy. xAPI requires LRS infrastructure and more technical planning.
xAPI is increasingly viewed as the future of eLearning standards, with development continuing actively while SCORM has largely plateaued. However, this does not mean every organisation should migrate immediately.
The most common mistake L&D teams make with xAPI is treating it as a SCORM upgrade. It is a measurement philosophy shift, one that requires buy-in from IT, L&D, and business stakeholders alike.
Explore SCORM 1.2 and SCORM 2004 – the standards xAPI was designed to improve upon.
Real-world use cases show where xAPI delivers genuine value for L&D teams
xAPI is genuinely transformative in scenarios where SCORM simply cannot operate. The clearest wins come when learning happens outside a traditional course and L&D teams need the data to prove impact. Based on industry examples and our own implementation experience, here are the use cases where xAPI consistently delivers:
VR and simulation-based training: xAPI can record every decision a learner makes inside a simulation, not just whether they completed it. A healthcare organisation using VR-based surgical training, for instance, can track how long a trainee spent on each step, how many attempts they made, and what errors occurred. That granularity is impossible with SCORM.
Mobile and field-based learning: Sales teams, field technicians, and frontline workers often learn on their phones, not at a desk. xAPI supports offline tracking, data is captured locally and synced when connectivity returns. This makes it ideal for industries like retail, manufacturing, and logistics.
Social and informal learning: xAPI can track learning that happens in conversations, peer reviews, or self-directed reading. Statements like ‘James reviewed a colleague’s presentation’ or ‘Fatima read an industry report’ can all be captured if the system is configured to send them.
Multi-system learning ecosystems: Large organisations often run multiple LMS platforms across regions or business units. xAPI with a central LRS creates a unified data layer, giving L&D leadership a single view of learning activity without forcing platform consolidation.
Linking learning to performance: Because xAPI data is granular and can be joined with HR or performance data, it becomes possible to draw a line between specific learning activities and on-the-job outcomes. This is the evidence base L&D teams need to make a case for investment.
Knowing when xAPI is worth the investment helps you avoid costly overengineering
xAPI is powerful, but it is not always the right tool. The implementation cost, in time, money, and technical resource, is significantly higher than SCORM. Before committing to an xAPI rollout, L&D teams need to be honest about whether the use case justifies it. Based on both our own project experience and published guidance from ADL and Rustici, here is a practical decision framework.
When to stick with SCORM
SCORM remains the right choice when training is browser-based, LMS-centric, and focused on compliance completion or assessment scores. If your learners are all desktop-based, your content lives entirely inside one LMS, and your reporting needs are straightforward, SCORM is simpler, cheaper, and widely supported. There is no reason to introduce LRS infrastructure if you do not need it.
When xAPI is the right call
xAPI makes sense when learning happens across multiple platforms or devices, when you need offline tracking, when you are running simulations or VR experiences, or when you need to connect learning data to business performance metrics. It also becomes compelling when you are consolidating data from multiple LMS platforms or when your L&D strategy includes informal and social learning. The investment in an LRS pays off when the data it captures leads to decisions you could not have made otherwise.
For most mid-sized organisations, a hybrid approach works well: maintain SCORM for existing compliance course catalogues and layer xAPI on top for new programmes with richer tracking requirements. According to eLearning Industry, xAPI continues to grow in adoption particularly among organisations with complex, multi-modal learning ecosystems. Also, cmi5 and xAPI are directly related. cmi5 is the implementation profile that tells LMS platforms how to use xAPI for formal learning.
Start with one high-value programme, instrument it with xAPI, and use the data story it produces to build the business case for broader adoption.
Frequently Asked Questions
Q1. What is xAPI and why is it also called Tin Can API?
xAPI stands for Experience API, a learning technology standard that records learning activity data across any platform, device, or environment. It was nicknamed ‘Tin Can API’ during its research phase (Project Tin Can) because the project was conceived as a two-way conversation between ADL and the eLearning industry, like speaking through a tin can telephone. The two names refer to exactly the same specification.
Q2. What is the difference between xAPI and SCORM?
SCORM tracks whether a learner completed or passed a course inside an LMS. xAPI tracks any learning experience, formal or informal, online or offline, across multiple systems, using an Actor–Verb–Object statement structure stored in an LRS. SCORM is simpler and cheaper to implement. xAPI is more powerful but requires LRS infrastructure and greater technical planning.
Q3. What is a Learning Record Store (LRS) and do I need one for xAPI?
An LRS is a database purpose-built to receive, store, and report xAPI statements. It is a required component of any xAPI implementation, without one, there is nowhere to send the data. An LRS can be a standalone product (like SCORM Cloud or Watershed) or embedded within a modern LMS. Your choice of LRS should be driven by your reporting needs and technical resource.
Q4. What is xAPI used for in L&D?
xAPI is used to track learning experiences that SCORM cannot reach: mobile learning, offline activity, VR and simulation-based training, social and informal learning, and multi-platform programmes. It is especially valuable when organisations want to connect learning data to business outcomes, such as linking a sales training programme to actual revenue metrics or linking safety training to incident rates.
Q5. What does an xAPI statement look like?
An xAPI statement follows an Actor–Verb–Object structure. For example: ‘Sarah completed the fire safety simulation.’ Or: ‘James scored 85% on the compliance assessment.’ Statements are written in JSON format and can carry additional context like score, duration, device type, and timestamp. The structure is flexible enough to describe almost any learning event while remaining consistent across systems.
Q6. Is xAPI replacing SCORM?
xAPI is increasingly seen as the future of eLearning standards, but SCORM is not disappearing soon. Most major LMS platforms still support SCORM 1.2 and 2004, and the volume of existing SCORM content is enormous. A hybrid approach, SCORM for existing content and xAPI for new programmes with richer tracking needs – is the practical path for most organisations in 2025 and beyond.
Conclusion
xAPI is one of the most important shifts in how L&D functions think about data. It moves the conversation from “did they finish the course?” to “what did they actually learn, where, how, and with what result?” That is a meaningful upgrade, but it comes with real implementation cost and organisational complexity. The teams that get the most value from xAPI are those that start with a specific, high-value use case, build the LRS infrastructure to support it properly, and then use the data story it produces to expand from there.
If your learning ecosystem is still SCORM-only, that is fine for now. But as your programmes grow to include simulations, mobile delivery, and multi-system environments, xAPI is the standard that will let you measure what actually matters.
