Embed Core
Embed Core is the entry plan for delivering Coassemble inside your own product. It opens up the full read/write API, the Generate API, all fifteen embeddable components including builders, webhooks, and multi-tenancy. It's sold through our team rather than self-service.
Embed Core is where Coassemble becomes infrastructure inside your own product rather than a place people visit. It includes the governed creation and branding of the self-service plans, then adds the API, embeddable components and developer tooling to build a fully integrated experience. Because it's a committed plan, you set it up by talking to our team.
What Embed Core adds
- The full API. Read and write access across courses, collections, screens, identities and tracking, plus the Generate API for creating courses, screens and quizzes programmatically.
- All fifteen embeddables. Players, builders, analytics, lists and cards across courses, collections and screens, including builder (edit-mode) embeddables so your own users can author courses inside your product.
- Events and webhooks. All postMessage events and the course.created, course.commenced and course.completed webhooks, so your systems can react in the page and server-to-server.
- Multi-tenancy. Scope users and content to your own tenants with the clientIdentifier.
- SCORM in-app. Both Dynamic and Standalone SCORM via in-app download.
- In-app translations. Localise courses with translations.
- Larger allowances and support. 2.5 million narration tokens and 1,500 image generation events per month, priority support, and an Order Form plus DPA.
Recipient allowances on Embed Core
Embed Core is a committed plan, so Identified Recipients are set as a committed allowance agreed with you rather than a fixed monthly figure, starting from 500 Identified Recipients per year. It includes up to 60,000 Anonymous Recipients per year. Because it's the Embed motion, going over an allowance is a commercial conversation rather than a hard stop.
What's not on Embed Core
The most programmatic features sit on Embed Automate and above: SCORM via API, the Themes API and themeId visual theming on embeddables, the Translations API, and destructive data operations like deleting clients, users or tracking for GDPR. Embed Core runs on the standard release server, and full legal negotiation (MSA), dedicated or region-locked servers and self-hosting are Embed Partner.
When to move up from Embed Core
Move to Embed Automate when you need the programmatic layer: SCORM via API, the Themes and Translations APIs, themeId theming, GDPR delete endpoints, and much higher usage allowances. Move to Embed Partner for negotiated terms, dedicated or region-locked servers, self-hosting and a full MSA.
Frequently asked questions
How do I get Embed Core?
Through our team rather than self-service checkout. Embed Core is a committed plan with an Order Form and DPA, so you set it up by talking to us.
Can my users build courses inside my product on Embed Core?
Yes. Embed Core includes the builder (edit-mode) embeddables and the Generate API, so your users can author and edit courses without leaving your product.
How are recipients counted on Embed Core?
Identified Recipients are a committed allowance agreed with you, starting from 500 a year, and up to 60,000 Anonymous Recipients a year. Going over is handled as a commercial conversation, not a hard cap.
Can I export SCORM through the API on Embed Core?
Not via the API. Embed Core includes Dynamic and Standalone SCORM through in-app download. SCORM via API starts on Embed Automate.
This article is maintained in our help centre. View the original ↗