adlnet.gov

store learner preference data in an xAPI Agent Profile document independent of any activity

store and retrieve a bookmark-style activity state document via the xAPI State API

Choose SCORM 1.2 or SCORM 2004 packaging based on sequencing needs and data-model differences.

Choose PUT vs POST and set the correct version header when submitting xAPI statements to an LRS.

Query an LRS for xAPI voided statements and retrieve a voided statement by StatementRef id

Construct an xAPI statement with a group actor, a custom verb, an activity object with definition extensions, and a context with instructor and registration UUID, then POST it to an LRS

Track a SCORM 2004 4th Edition SCO using the adl.nav.request interaction and cmi.interactions array to record scored question responses

Implement SCORM 1.2 runtime communication using the LMSInitialize / LMSFinish API and persist cmi.core.lesson_status and cmi.suspend_data within the 4096-byte limit

Configure SCORM Runtime communication from a SCORM 2004 SCO to an LMS using the SCORM RTE JavaScript API

Query an LRS for xAPI statements filtered by actor and verb using GET /statements

Send an xAPI (Tin Can) statement to a Learning Record Store endpoint

Choose between SCORM 1.2 and xAPI for course tracking

Ingest xAPI statements into an LRS

Send xAPI statements to a Learning Record Store (LRS)