Developers
Embed Jami3D's interactive 3D stories in your site or LMS, follow what viewers do, and call the API from your backend.
What you can build
A Jami3D experience is a story told in a 3D scene: scripted characters, a camera that moves with intent, and Beats where the story waits for the viewer — to look around, answer a quiz, or ask a character a question that an AI answers in the character's voice.
- Embed an experience in any page with the
jami3dSDK: a few kilobytes that put the Live Room player in an iframe and let your page drive it and hear what happens. Start with the Quickstart. - Secure embeds for an LMS or a hospital: your backend issues a single-use grant per learner, and the results come back keyed by your own user id. Secure LMS embeds.
- Webhooks tell your backend when a learner answers a quiz, finishes a story, or rewinds over an answer. Webhooks.
- The server API issues grants and reads your projects, your usage and your learners' results with a secret key. REST API.
- Game packages put a scene exported from the Studio into your own three.js game with
@jami3d/three, the game runtime (MIT). It is another package thanjami3d, the embed SDK, and each has its own versions. Game packages in three.js.
Try it
The playground plays a published experience in this page with the real SDK: toggle the options, watch the events arrive, and copy the code it writes for you. Signed in, it offers your own projects and your test keys.
Stability
The SDK, the embed and /v1 never break: changes are additive only, and every SDK released in the last 24 months keeps working against today's player. Read answers tolerantly — ignore a field or a value you do not know — and the integration you ship today keeps working. The changelog lists every version.