Implement SCORM Cloud v2 API dispatch: create a dispatch, deliver it to an external LMS, and retrieve learner registration results
domain: cloud.scorm.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to /api/v2/dispatches with the target courseId, allowNewRegistrations, instanced, and the destination LMS's email or externalConfig
Retrieve the dispatch ZIP package via GET /api/v2/dispatches/{dispatchId}/zip and deliver it to the external LMS for import
The external LMS launches the dispatch package; the dispatch proxy forwards launch parameters to SCORM Cloud and creates a registration under your account
GET /api/v2/dispatches/{dispatchId}/registrations to list all learner registrations created through this dispatch
GET /api/v2/registrations/{registrationId}/progress to retrieve completion, success, score, and time data for each learner
Enable or disable a dispatch via PUT /api/v2/dispatches/{dispatchId} with enabled=false to cut off access without modifying the external LMS
Known gotchas
Dispatch packages act as a SCORM proxy; the external LMS sees a generic SCORM course, not the actual content — content updates on SCORM Cloud are reflected automatically without re-importing the dispatch ZIP
Each learner in the external LMS gets a new SCORM Cloud registration on first launch; if the external LMS resets SCORM data (re-registers the user), a second registration is created and the original is orphaned
Registration results may lag by seconds after session completion; poll with a short delay rather than expecting immediate availability after the LMS reports completion
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp