Overview/OpenAPI/Interactive Lessons

Interactive Lessons

Create, manage, and iterate flows organized around interactive lessons use cases.

Interactive Lessons API

This page explains the API from the interactive_lesson perspective.

Legacy compatibility:

  • web_app is still accepted as an input alias
  • catalog and API responses now use interactive_lesson

Interactive lessons still use the same creation, job, and detail endpoints, but the parameter set should stay much lighter.

Create

POST /creations

Common fields:

  • type=interactive_lesson
  • prompt
  • language
  • instructions

Usually not needed:

  • voice_id
  • duration_seconds
  • scene_count

Manage

The main priorities are:

  • whether the job is complete
  • the final launch URL
  • a preview or cover image

Edit

Interactive lessons more often evolve as whole experiences instead of scene-level edits.

If your product exposes “continue editing,” it is usually better to turn user feedback into a new prompt or instructions pass before the next creation or edit.

Practical Guidance

  • keep both the UI and docs lightweight
  • do not copy the full video or slides parameter surface
  • return a clear “open this URL to try it” result first