5 Frequently Asked Questions About Experience API (xAPI)
The Experience API (xAPI) is an exciting new eLearning software standard for eLearning professionals that will enable us to collect and analyze far more learning data than was possible in the past. Yet there is a great deal of confusion about what xAPI does, and what needs to happen for your organization to start using it. In this article, we answer 5 of the most frequently asked questions about getting started with xAPI.
1. What is Experience API (in simple terms)?
The Experience API (also known as xAPI, or by its original working name of Tin Can API) is a data standard for reporting learning activities. It establishes a common technical framework for how different software systems can report on learning actions in the same way, such as “Jane Doe attempted Sales Training 101” or “Bob Smith completed New Hire Safety.”
API stands for Application Programming Interface. It is a generic software term for the connection between different technical systems. Two software systems can share data with each other using APIs. The xAPI refers specifically to how learning activities should be reported between different technical systems.
By itself, the xAPI is simply a data standard. Implementing the xAPI also requires a database to store a large number of individual learner interactions. The creators of the xAPI standard recommend using a Learning Record Store (LRS), a database that has been specially designed to store records generated by xAPI statements. The LRS can be inside an LMS, or used stand-alone (more common as of today).
In addition to a database, you will also want reporting and analysis tools that help you understand and gain insights from the collected data. Currently the options for data analysis are pretty minimal. But although the xAPI ecosystem of implemented tools and services is still in its relative infancy, it will theoretically enable two areas of great potential for eLearning practitioners in the future:
- Getting much more granular data on individual learner interactions beyond SCORM, and
- Creating a central repository to track informal learning activities beyond courses delivered through an LMS.
2. Is Experience API a replacement for SCORM?
No, it is not. As a standard, SCORM is primarily used to bridge the gap between eLearning authoring tools and LMS systems. This enables content developers to export SCORM files from their authoring tool of choice and upload it in any SCORM-compliant LMS.
SCORM contains some analytics capabilities but is very limited in what data can be reported and collected. xAPI provides a modern standard around data reporting and goes far beyond the information SCORM can provide. But it is not intended to be a replacement for SCORM - there is nothing in the xAPI that is related to authoring and displaying eLearning content.
3. Will Experience API enable my course to be playable on mobile devices?
No. The xAPI is not related to content authoring and delivery. It does enable data to be collected from learning activities happening on mobile devices, which generally was not possible with SCORM.
For mobile delivery, look into whether your authoring tools and LMS support HTML5 and mobile responsive output.
4. How do I use the Experience API to capture informal learning activities?
To capture informal learning activities, the source of the learning activity needs to send xAPI statements to your LRS. Several content authoring tools and LMS systems are already enabled for xAPI. However, if you are looking to track activities from other informal sources like webpages and internal systems, each of those needs to be enabled for xAPI and connected to your LRS.
5. Is Experience API the only way to get more data about learning activities?
No. If you have access to developer resources, you can add tracking tags and record whatever activities you specify in whatever database you choose. Many web analytics packages already work this way. Another option is to use an LMS that reports detailed data already, though sometimes this is possible only for courses built through an LMS’ authoring tool (i.e. not uploaded via SCORM).
The advantage to using xAPI is that as more tools adopt the standard, more compatible data can be sent out-of-the-box to your LRS database and reporting systems. However, the industry is still in the early stages of adoption.
Summary
The xAPI is an exciting new data standard that provides a uniform guideline for collecting and tracking learning activities.
For more information, please review these resources:
- US Dept of Defense’s official xAPI page
- Zapier’s An Introduction to APIs
- Rustici Software’s Tin Can Overview
- Saltbox’s Wax LRS
