Skip to main content
xAPI content (also known as TinCan or cmi5) is interactive learning that reports what a learner did as it plays. You add it to Juno from a ZIP package, and Juno marks the unit complete when the package reports completion. This page is about content you add to Juno. To send Juno learning activity to an external Learning Record Store, see xAPI integration.

Two kinds of xAPI package

Juno reads the package’s manifest to find its launch target. The launch target decides how Juno handles the unit.
Vendor-hosted xAPI needs one setting. Self-hosted xAPI needs a second setting on top of it. If your package contains the course files and you see This package contains the course files itself, which isn’t supported yet, the second setting is off for your organization. Ask your administrator.

Add xAPI content

1

Open the SCORM dialog

Select + Create, hover New, and choose SCORM. When xAPI is enabled, the dialog shows a switch above the form.
2

Choose xAPI

Select xAPI / TinCan · cmi5 instead of SCORM 1.2 / 2004. The dialog title changes to Create xAPI / TinCan content.
3

Upload the package

Under Upload manifest file, drop a ZIP onto Drag & Drop your ZIP file or click to browse. The ZIP must contain a tincan.xml or cmi5.xml manifest. It can sit in a folder inside the ZIP. Juno reads the manifest and fills in the title and Launch URL for you. The launch URL carries an auto-detected tag.
4

Check the details

The dropzone confirms Manifest parsed successfully. Edit the title, add a description, and set the language, audience, tags, and co-editors if you need to.
5

Create

Select Create. For a self-hosted package, Juno then uploads and unpacks the files and shows its progress. The unit opens when it finishes. If you started from a Journey, the unit is added to that Journey as a step.

If the manifest can’t be read

The dropzone says Could not parse manifest — click to try a different file, with the reason under it.

Change a vendor-hosted unit

To point a vendor-hosted unit at a different launch URL, open its editor. The package area shows the current launch URL. Drop a new ZIP onto it, then select Update. When xAPI is enabled, an editor switch also lets you change a unit between SCORM 1.2 / 2004 and xAPI / TinCan · cmi5. Switching replaces the unit’s content when you upload the new package.

How learners take xAPI content

What a learner sees depends on the kind of package.

Self-hosted packages

The content plays inside the unit page, the same way SCORM content does. Juno checks for completion in the background and updates the unit when the package reports it. Camera and microphone are not available to the package.

Vendor-hosted packages

1

Launch the content

The page says This content will open in a new window. Select Launch content.
2

Take the content

Work through the content in the new window. Back in Juno, the unit page says Content opened in a new window. Waiting for completion… Select Reopen content window if you closed it.
3

Come back to Juno

When you return to the Juno tab, Juno checks completion. The page changes to Content completed! Select Relaunch content to open it again.
If the content does not load, learners see Failed to load content. Please try again. If the stored address is not a valid web address, they see a message asking them to contact their administrator to re-upload the package.
Vendors often block their content from loading inside another page. That is why vendor-hosted content opens in a new window.
Last modified on October 8, 2026