Get started

Get access

Everything about how the embed works is public and always will be. The hub is the half with your keys in it — app ids, the secret that signs your tokens, a token minter, and usage per app — so it is opened by hand, one developer at a time.

Ask#

The answer arrives by email, so the hub needs an account with a verified address behind it. Sign in and you will land straight back here.

What is inside#

The developer hub: a sidebar of views, four numbers, a chart of sessions a day and an activity feed — The hub. Apps, tokens, usage and walkthroughs, drawn from one JSON document.

Apps. A public id that rides the iframe URL, a secret shown exactly once, the origins allowed to frame it, the space it opens into, and its shape.
A token minter. A signed token for any user id you like, valid fifteen minutes — so you can watch the widget work before your server signs anything.
Usage. Sessions, walk-ins and huddles per app, by the day, against the fortnight before. Counts, never a roster.
Three walkthroughs. A lesson page, a marketing site with no backend at all, and a React app that reacts to the room.

Meanwhile#

The token shape, both auth flows, the install, the shaping and the full reference are all on these pages, signed out, with working code. You can read every line of how an integration is built while you wait for us — and in development the sandboxes run without any of it.