Vidbyte

API documentation

POSTLivePOSTFocused route reference

POST /api/v1/projects/generate

Generate a Project

Generate the full project artifact after the draft and optional intake phases. This route is the final generation step in the staged Projects API lifecycle.

Manage keys
Stable public contract

Public endpoint

/api/v1/projects/generate

Maps to

/api/sandbox/generate_project

What to know first

Use this after project create and, optionally, after the intake questions phase.

Method

POST

Send this operation to /api/v1/projects/generate on the versioned public host.

Authentication

API key

API key via Authorization: Bearer or x-api-key

Resource model

Direct

Use this after project create and, optionally, after the intake questions phase.

Highlights

What this operation does

Generate the full project output for an existing draft project.
Use this after project create and, optionally, after the intake questions phase.
Store the encrypted `id` returned by create and list routes exactly as returned if you need to fetch the resource again later.

Request details

Request parameters

Request parameters

These are the parameters that shape /api/v1/projects/generate. Path parameters and request-body fields are shown together because the docs stay focused on the public route contract.

promptstringRequired

Primary user request, learning goal, or topic for generation.

project_idstringRequired

Encrypted public id returned by project create.

answersstring[]Optional

Optional answers to the generated intake questions.

Response shape

What the response contract guarantees

Public responses use the shared envelope: `success`, `id`, `message`, `data`, `token_stats`, `pricing`, and `error`.
The `id` field is always a public/encrypted identifier boundary, never a raw MongoDB `_id`.
The generated project response reuses the standard public resource envelope and project object.