How do I get started with a Coassemble Sandbox?

How to get a Sandbox, what it's for, and what to prove while you're in it.

A Sandbox is a free, code-first test account for developers evaluating Coassemble inside their own product or platform. Select Get your sandbox on coassemble.com, choose Get my hands on the API, fill in your details and select Open my sandbox. Once you're in, the job is to take one piece of learning all the way through: built from your own content, embedded on a surface you run, delivered to a test learner, with the completion landing back in your own systems.

If you just want to build courses and share them with your team, without a developer, talk to the team instead. They'll help you find the right option.

How do I get a Sandbox?

1. Go to coassemble.com and select Get your sandbox.
2. Under What brings you here?, choose Get my hands on the API. (The other two options send your details to the team instead of creating a sandbox.)
3. Enter your work email, company, role and your product's website, choose when you want to be live, and tell us how you heard about us.
4. Select Open my sandbox.
5. When your sandbox is ready, select Open your sandbox (or wait a few seconds and you're taken there). Set your name and password, then select Continue to reach your new workspace.

This usually happens straight away. We also email you the link to your sandbox, which is valid for 7 days. If the sandbox isn't ready yet, the screen says so and the team follows up by email.

What you'll need: a work email address. Free email domains such as Gmail or Outlook.com aren't accepted for a Sandbox.

Which option should I choose?

When you select Get your sandbox, you're asked What brings you here? There are three options:

• Get my hands on the API: for developers. This is the only option that creates a Sandbox straight away. The Sandbox is code-first, so without a developer it won't get you far.
• Connect Coassemble to a tool you already use: sends your details to the team, who get back to you.
• Just want to build a course and share it?: sends your details to the team, who get in touch with options that suit building and sharing courses.

What is the Sandbox for?

The Sandbox exists so you can prove an integration works in your own environment, with your own content, before there's any commercial conversation. Spend your time getting one course through the full chain: created, branded, embedded, completed, and recorded in your own stack.

How does the Sandbox budget work?

Your Sandbox runs on a single evaluation allocation, sized to prove an integration end to end. It's a one-time budget, so once it's spent, it's spent.

Spend it on moving forward. One course taken all the way through to a captured completion is the most useful thing you can do with the budget you have. Image generation and AI narration both draw on it, so use them deliberately.

What can I do in a Sandbox?

The Sandbox gives you the everyday Coassemble feature set, on an evaluation budget.

Creation: build a course with the AI agent from a document, a presentation, a SCORM package or a written brief, choosing Verbatim, Structured or Adaptive to say how closely it follows your source. Screens are made of blocks you arrange on a grid, grouped into sections. Ask the agent for more screens, a knowledge check or a quiz, use its Review tab for feedback on the course, and its Insights tab to read how learners went. Generate images, refine content and add AI narration with premium voices. Connect to OneDrive or Google Drive, upload your own images and video, and organise courses into folders and collections. Course creators are unlimited, and so are courses. The Classic builder is still there if you prefer it.

Branding: themes and colours, Google Fonts, custom font upload, per-block fonts on headings and paragraphs, your logo, and a brand voice so generated content sounds like you.

Delivery: share links, email invitations, Slack, embed in any tool, and the Course and Collection embeddables including the Player, Card, List and Builder edit mode, plus Screen Builder and Screen Player for working with a single screen. Recipients open courses on any device without logging in, and their progress saves. Dynamic SCORM export is available in-app.

Access and identity: anonymous sharing, email capture, Slack pre-auth, pre-determined access lists, domain locking, and API-identified access. Each learner gets a signed link tied to the identifier you already hold for that person in your own system.

Tracking: course, collection and user analytics, completion rates, sentiment, individual recipient usage, CSV export, and webhooks for course created, commenced and completed events. A Sandbox only has test API keys, and learners launched with a test key are kept out of Insights and reports, so use the completion webhook to confirm embedded test completions.

Connected AI: connect an assistant such as Claude to the workspace over MCP and have it create and manage courses with over 50 tools.

What should I prove first?

Work through these in order. Each one is a rung towards a real completion landing in your own stack.

1. Make an authenticated call. Create an API key in the Developer console (select Developer in the navigation, then API keys, or use Create a test key and start on the Overview tab) and confirm a call returns your own workspace data.
2. Build a course from your own material. Use a real document you'd genuinely want to train people on. Your own handbook, in whatever state it's in, is the honest test of what comes out the other side.
3. Brand it. Apply your theme, fonts and logo so it looks like it belongs in your product.
4. Embed it on a real surface. Your own product, an internal tool, your intranet or Slack. Somewhere you actually run.
5. Deliver it to a test learner. Generate a signed link against an identifier from your own system.
6. Capture the completion. Receive the completion webhook in your own stack. Learners launched with a test key don't appear in Insights, so the webhook is where you confirm the completion. This step is the one most likely to need a colleague, so line that up early.

Which APIs can I use in a Sandbox?

All of them. A Sandbox carries the full Coassemble API, exactly as every paid plan does, so there's nothing to unlock and nothing held back for later:

• REST for courses, collections, screens, embeddables, webhooks and events, including webhooks for course created, commenced and completed.
• The Generate API for creating and updating courses programmatically.
• The Tracking API, both read and GDPR delete.
• The Themes API, read and write, including visual theming on embeddables with a themeId.
• Translations by API.
• The usage allowance API and per-tenant usage reporting.
• Embed MCP, alongside postMessage events and API-identified access.

The only thing that limits a Sandbox is its one-time evaluation budget, and its API keys are test keys. When you go live on a paid plan, you create a Production key; the API surface and the feature set stay the same.

Frequently asked questions

Does a Sandbox cost anything?

No. The Sandbox is free. Pricing for ongoing use is at coassemble.com/pricing.

Can I use a personal email address to get one?

No. The Sandbox sign-up requires a work email address, so a free email domain won't be accepted.

What if I already have a Coassemble account?

If your email already has an account, the sign-up tells you so and offers Sign in instead of creating a new Sandbox.

Can I invite my team into the Sandbox?

Yes. Course creators are unlimited, so you can bring in whoever needs to be part of the evaluation, including the developer who'll do the integration work.

Do the people taking my course need an account?

No. Recipients open a course by link on any device without logging in, and their progress saves as they go.

Does the Sandbox budget refresh?

No. It's a single allocation for your evaluation.

What happens when I'm ready to move ahead?

Talk to our team about which plan suits your usage, or see what each one includes at coassemble.com/pricing.