Publish once. Send your course to every customer's LMS.
Stop rebuilding the same course for six different systems. With SCORM Dispatchyou publish a package once and route it into your customers' LMSs — with seat caps, expiry dates, and a one-click kill switch. You keep the source files; completions flow back to one dashboard.
What's a “dispatch,” exactly?
A dispatch is a small SCORM file your customer uploads to their own LMS. Instead of the actual course, it contains a secure pointer back to Allure Connect. When a learner clicks play, your real course streams from us — so you can cap seats, set an expiry, or shut it off, all without ever handing over your source files. Your customer just sees a course that works; you keep the controls.
From one upload to live in a customer's LMS — in three steps.
Publish your package
Upload your SCORM or xAPI course once. We host the runtime and validate it's launch-ready — manifest, assets, launch file, all checked.
Create a dispatch route
Name the customer, set a seat cap, expiry, and allowed domain, then download a tiny SCORM shell ZIP — or send a launch link. No engineering on either side.
Completions flow back
Your customer uploads the shell to their LMS. Learners launch; every completion, score, and timestamp streams back to your Connect dashboard in real time.
Licensing controls on every route.
Allowed-domain enforcement
A launch only works from the customer's approved domain. Paste the shell anywhere else and it refuses to run.
Seat caps & expiry
Cap registrations per route and set an expiry date. Optional access password for an extra lock.
One-click revocation
Kill a dispatch instantly — launches stop without you ever touching the customer's LMS or chasing a takedown.
Republish, everywhere
Update the package and every active dispatch picks up the new version automatically — no re-sending shells.
Per-client reporting
See launches, completions, and pass rates broken out by customer and course — audit-grade evidence per dispatch.
Embeddable launch URLs
Prefer a link to a shell? Drop a launch URL into your own product, portal, or marketing page — same guardrails apply.
How the runtime actually stays in your hands.
The shell your customer uploads is a thin SCORM wrapper. At launch it opens a Connect-hosted player and we mint a short-lived, signed session token — the course content is streamed server-side and never lands in the customer’s LMS. Completion data is reconciled back through the SCORM API and mirrored into your xAPI Learning Record Store.
- SCORM 1.2 & 2004 (all editions), xAPI, cmi5, and AICC shells
- Short-lived session tokens minted at launch, not embedded in the shell
- Allowed-domain referer checks reject off-domain launches
- Idempotent completion callbacks; Connect remains the system of record
POST /v1/dispatches { "package_id": "pkg_01HXFV9P", "destination": "Acme · Cornerstone", "allowed_domain": "acme.csod.com", "seat_cap": 1000, "expires_at": "2026-04-12" } ← 201 · shell ready { "id": "dsp_4KXQ", "status": "live", "shell_url": "…/dsp_4KXQ/scorm.zip" }
What sits on top of dispatch.
Send one course to everycustomer's LMS.
Get a sandbox key and create your first dispatch in minutes — no credit card.