How to read this page
Treat sandbox routes as implementation context and the `/api/v1/quizzes` shape as roadmap direction.
Do not build external integrations against the preview versioned route until the backend policy surface exposes it.
Live sandbox generation exists, but a public API-key route layer is still pending
Quiz generation and progressive editing already exist in the backend under sandbox routes. The product design points toward cleaner versioned quiz endpoints, but those resource-style paths are not shipped yet for external API-key callers.
Current live backend
/api/sandbox/create_quiz
Internal app-auth route.
Editing flow
/api/sandbox/edit_quiz
Internal progressive quiz updates already exist.
Planned public shape
/api/v1/quizzes
Design direction, not live route reality yet.
How to read this page
Treat sandbox routes as implementation context and the `/api/v1/quizzes` shape as roadmap direction.
Do not build external integrations against the preview versioned route until the backend policy surface exposes it.
Routes
What this page actually points to
/api/sandbox/create_quiz
Generate a quiz from content using sandbox orchestration.
Auth
Session/JWT auth in the app today
Notes
This route is live in the backend but is not yet approved by `is_api_key_route` for external API-key access.
/api/sandbox/edit_quiz
Apply progressive edits to an existing quiz.
Auth
Session/JWT auth in the app today
Notes
Current app route, not a public API-key route.
/api/v1/quizzes
Planned versioned quiz create route described by the product design.
Auth
Planned API key support
Notes
This shape is design direction, not a shipped backend path.
Request details
Planned top-level quiz fields
Useful for planning, but still preview for external API-key callers.
Multiple choice, true/false, or open-ended.
Preset-first configuration layer for question design and quiz info.
Learning goal or assessment target.
Shared context envelope as it becomes public.
Related pages
Exams
The backend can already generate exams through `/api/sandbox/create_test`, but the cleaner `/api/v1/exams` contract described by the product design remains preview-only.
Projects
Project Studio already has backend generation primitives, but the public API-key surface does not yet expose a clean versioned project create route. The docs therefore show the current internal routes and the planned public direction separately.
Context Objects
The product design describes a shared `context` array for learner data, source documents, and Vidbyte artifacts. That envelope is already present in some request models, but the current public routes still primarily map prompt-driven fields into the existing internal orchestrators.