Skip to main content
A Motion is a reusable driving action from a video. It is not a background scene. Use a Motion’s mot_... ID as motion_id when creating a Render. All endpoints in this page require Authorization: Bearer YOUR_API_KEY.

Create a Motion

POST /v1/motions Creates an asynchronous Motion. Send multipart/form-data. Provide exactly one Motion source: motion_video or motion_video_url. Use a valid driving video that the service can read. For URL input, the URL must be reachable by Viggle’s servers for the duration of the request.

Example: create from a URL

Import a Motion template

POST /v1/motions/import Imports a Motion from a Viggle template. Send a JSON request body.
The response is a Motion resource. Poll it by ID until it is ready.
template_id takes precedence when both template fields are sent. Send only the preferred template_id in new integrations.

Get a Motion

GET /v1/motions/{motion_id}

List Motions

GET /v1/motions This endpoint currently has no query parameters and returns all Motions for the current account.
The response uses the same { "data": [Resource, ...] } shape as List Characters.

Delete a Motion

DELETE /v1/motions/{motion_id}

Motion response fields

All Motion endpoints return the same resource fields as Characters: id, status, name, progress, capabilities, created_at, completed_at, and error. A Motion ID looks like mot_550e8400-e29b-41d4-a716-446655440000; preserve it exactly.

Endpoint response rules