Dispatch a SCORM Cloud course to an external LMS using the SCORM Cloud API v2 dispatch feature
domain: cloud.scorm.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the SCORM Cloud API v2 using your application ID and secret key via HTTP Basic Authentication; all endpoints return and accept JSON
Import the SCORM or xAPI course package into SCORM Cloud via the courses import endpoint to obtain a courseId
Create a dispatch destination representing the external LMS; then create a dispatch linking the courseId to the destination, which generates a launchable SCORM package the LMS can import
Download the dispatch zip package from SCORM Cloud and provide it to the external LMS for import; the LMS treats it as a normal SCORM package, but all tracking data is tunneled back to SCORM Cloud
Monitor learner completion and score data in SCORM Cloud via the registrations endpoints; retrieve results by registration ID for reporting
Known gotchas
Dispatch currently supports postback configuration but does not yet support player configuration through the settings cascade; display and UI customizations set on the course level may not propagate to dispatched instances
The v1 and v2 SCORM Cloud APIs are not interchangeable; v2 is JSON-only and has different endpoint structures and authentication behavior — never mix v1 and v2 calls in the same integration
Dispatch packages are tied to the destination; if the LMS is decommissioned or its destination record deleted in SCORM Cloud, existing launched registrations lose their tracking relay and data stops flowing back
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?