Developers/API for reference-led creation.

Build on the same project, reference, asset, quote, run, and webhook contracts that power Studio.

API sequence

POST /creative-sessions
POST /creative-sessions/{sessionId}/intake-preview
POST /creative-sessions/{sessionId}/production-plans/preview
POST /creative-sessions/{sessionId}/production-plans/execute-next
GET  /projects/{projectId}/assets
GET  /webhooks/{webhookId}/deliveries

API-first projects

Create projects, attach references, request production plans, and inspect readiness through typed contracts.

Governed execution

Keep quote review, source approval, payment readiness, and team controls in the loop before paid generation starts.

Scoped integration

Use workspace and project boundaries so external systems can automate work without broad account access.

Integration flow

Create or select a creative session.
Attach references, products, characters, and project context.
Preview the plan and quote before paid work.
Execute only after governed approval.
Read run status, generated assets, and webhook deliveries.

Projects

Workspace projects, project chat, plan previews, selected variants, and project assets.

Creative sessions

Louie state, intake preview, production plan preview, checkpoints, and governed execution.

Webhooks

Delivery records for project, quote, run, asset, and billing-related events exposed safely to integrations.

What stays customer-safe

Integrations can show plan state, source requirements, generated assets, quote status, storage usage, run progress, and approval state. Internal routing and infrastructure details and raw infrastructure identifiers stay out of customer-facing UI.