Help topics
API and MCP
The API runs the same production service as the app, or single parts of it. All requests use your Scenvy credit balance.
Create a key under API & MCP with only the scopes you need. It is shown once. Send it from your server, never from browser code, a repository or a URL:
Authorization: Bearer sc_live_...
# or
X-API-Key: sc_live_...Use test keys while integrating. If a key leaks, revoke it and create a new one. The exact fields of every endpoint are in the live OpenAPI schema.
Endpoints
| Endpoint | Use it for |
|---|---|
/v1/productions | The complete workflow from brief to video |
/v1/editor/projects | Editor projects and embedded editor sessions |
/v1/maps | Map compositions and renders |
/v1/modules | Single information graphics |
/v1/thumbnails/generate | Thumbnail variants from a title and brief |
/v1/mcp | MCP server with initialize, tools/list and tools/call |
To embed the editor, your server creates a session and the browser receives only its short-lived token. An MCP client sees only the tools its key's scopes allow.
Jobs and errors
| Situation | What to do |
|---|---|
| A render was accepted | Poll the returned job until it is ready or failed, then use its result URL |
| HTTP 402 | The balance is too low. Top up before retrying |
| Validation error | Fix the request; retrying it unchanged fails again |
| The response was lost | Look up the job first, then retry with the same Idempotency-Key |
| The render failed | Its credit reservation is released |
Log job IDs. Support needs them to trace a request.