Viggle API V1

V1 is the current API. Start new integrations with V1. Existing integrations using /api/* can follow the migration guide.

Viggle API is organized around reusable assets, asynchronous operations, and delivered artifacts. Create Characters and Motions once, then reuse them in multiple Renders. A Render is an operation; its MP4 and optional alpha video are its artifacts.

Create your first render

Get an API key

Create an API key in the Viggle Dashboard.

Create a render

Upload an image and a motion video to POST /v1/renders.

Wait for the result

Poll GET /v1/renders/{render_id} until status is ready, then use video_url.

Quickstart: create a render

Copy a complete Python, JavaScript, or cURL example.

Choose a workflow

Render now

Upload an image and a motion video in one request. Best for a first render or one-off work.

Reuse assets

Create Characters and Motions once, then reference their IDs in later Render requests.

Core concepts

Concept	What it represents
Character	A reusable character created from an image. IDs start with `char_`.
Motion	A reusable driving motion created from a video. IDs start with `mot_`.
Render	An asynchronous video-generation job. IDs start with `render_`.
3D Conversion	Image-to-3D and video-to-3D conversion operations. These are separate from reusable V1 assets.

Next steps

Authentication

Send API keys securely.

API reference

Browse every V1 resource.

Production guide

Handle async jobs and failures.

Authentication

Get Started

Guides

Production

Create your first render

Quickstart: create a render

Choose a workflow

Render now

Reuse assets

Core concepts

Next steps

Authentication

API reference

Production guide

​Create your first render

Quickstart: create a render

​Choose a workflow

Render now

Reuse assets

​Core concepts

​Next steps

Authentication

API reference

Production guide

Create your first render

Choose a workflow

Core concepts

Next steps