At Makeshapes, we want to help you understand the impact of your learning experiences. Our xAPI integration lets you capture detailed data about how learners interact with Makeshapes content and send it directly to your Learning Record Store (LRS).
Note: xAPI integration depends on your Makeshapes service plan and configuration.
What is xapi?
xAPI (also called the Experience API or Tin Can API) is a modern learning technology standard. Think of it as a language that lets different systems talk about learning activities. Instead of just tracking experience completions, xAPI can capture a wide range of experiences, both online and offline, using "Actor Verb Object" statements like "Jane Doe completed Safety Experience."
How Makeshapes uses XAPI
When learners engage with your Makeshapes experiences, our platform automatically creates xAPI statements for key events. These statements get sent securely to your LRS endpoint.
What this means for your organization
Centralized learning data: Bring together learning data from Makeshapes and your other learning tools in one place - your LRS.
Better insights: Get richer data about learner progress, engagement patterns, and what content works best.
Stronger reporting: Use your LRS and business intelligence tools to create the reports you need.
Easy connections: Connect Makeshapes to your existing learning technology without hassle.
Compliance and record keeping: Keep detailed, auditable records of all learning activities.
Learning events we track
Makeshapes sends xAPI statements for these important events:
Experience published
What it means: A new experience or learning module goes live in Makeshapes and becomes available to learners.
Data we send: Who published the experience (like a Makeshapes admin or the platform itself) plus details about the experience (ID, title, description, type). This helps your LRS recognize the experience when learners start using it.
Participant starts experience
What it means: A learner launches or opens a Makeshapes experience.
Data we send: Who the learner is, which experience they started, and when they started it. This marks the beginning of their learning session.
Participant completes experience
What it means: A learner finishes all required parts of a Makeshapes experience.
Data we send: Who completed it, which experience they finished, and a result showing successful completion.
Participant abandons experience
What it means: Our system automatically generates this when a learner starts an experience but doesn't complete it within 30 days.
Data we send: Who the learner is and which experience they didn't finish within the expected time.
Setting up your XAPI integration
To get xAPI data flowing from Makeshapes to your LRS, you'll need to configure the integration in your Makeshapes settings.
What you'll need first
Get this information from your LRS Administrator:
LRS Endpoint URL: The web address where xAPI statements get sent (like
https://your-lrs.com/data/xapi/statements).Authentication Method: Whether your LRS uses Basic Authentication or OAuth 2.0 Client Credentials.
Authentication Credentials: For Basic Authentication: You need a Username (often called an API Key or Client Key) and Password (often called an API Secret or Client Secret). For OAuth 2.0 Client Credentials: You need a Token Endpoint URL, Client ID, and Client Secret. OAuth 2.0 setup might include additional fields like Scope.
How to identify learners: Choose how you want Makeshapes to identify learners in the xAPI statements. The default is Email Address , but you might be able to use internal Employee IDs .
If using Employee ID: You need Participant SSO turned on and configured to capture this data. You'll also need to provide your organization's homepage URI—a unique web domain that acts as a namespace for your employee IDs (like https://yourcompany.com or https://identity.yourcompany.com ).
How to configure it in Makeshapes
Log in to your Makeshapes admin account.
Go to the Organization Settings page.
Find the Integrations tab and click Configure in the xAPI Integration section.
Enter your LRS Statement Endpoint URL .
Choose your Authentication Method (None, Basic Authentication, or OAuth 2.0).
Enter your credentials (Username/Password for Basic Auth; Token Endpoint, Client ID, Client Secret for OAuth 2.0).
Save your configuration.
Test the connection to make sure everything works.