Authorization: Bearer YOUR_API_KEY.
Request and response conventions
Public ID formats
IDs are opaque values generated by Viggle. Preserve them exactly as returned; do not construct, shorten, or strip their prefixes.Success and error responses
Creation endpoints return200 OK with an asynchronous resource in queued state. A resource status request can return 200 OK with status: "failed"; always inspect both the HTTP status and the response body.
Resources
Code examples
Go, JavaScript, Python, and cURL requests for the current V1 endpoints.
Resource model
V1 separates reusable content from work performed on that content:
Direct
image and motion_video inputs on POST /v1/renders are one-time inputs. They do not create a Character or Motion that appears in an asset list. Create an asset explicitly when it needs to be reused.
Endpoint index
Conventions
- Requests that upload media use
multipart/form-data. - IDs are resource-prefixed, such as
char_...andrender_.... - All asynchronous resources use
queued,processing,ready, andfailed; Renders may also becancelled. - Error responses use
{ "error": { "code", "message", "request_id" } }. Internal worker and pipeline codes are never exposed.

