Skip to main content
POST
Generate a video from text, from a first and optional last frame, from a reference video/image, or from a character image and/or driving video
Send multipart/form-data with at least one of reference_video, reference_video_url, reference_image, or reference_image_url. Supplying any of these four fields is what selects this mode of POST /v1/videos — reference-video (omni-reference) generation — and produces a Viggle-optimized MiniMax H3 video with native audio.
If you supply none of the four reference fields, this is not an error — the request silently falls back to Generate Video (from Text) instead, the same way omitting first_frame_image/last_frame_image there falls back to text-only. There is no source/mode parameter to force reference-video selection independently of these fields, so double-check your request actually includes one of them before relying on this mode.
This uses the same POST /v1/videos endpoint as Generate Video (from Text), Generate Video (from First Frame and/or Text), Generate Video (from First-Last Frames and/or Text), and Generate Video (from Character Animation) — which mode runs is selected by which fields you send, not by a separate parameter. Reference fields cannot be combined with first_frame_image/last_frame_image.
Every generated video includes native audio — there’s no separate audio flag or field. Pricing (1 credit = 0.01):durations×thepersecondrateforquality0.01): ⌈`duration_s`⌉ × the per-second rate for `quality` — **0.01/sec (1 credit/second)** for both low and high. Reference-conditioned generation costs the same as text-only for the same quality and duration; resolution and aspect_ratio don’t affect price. See Pricing and retention.

Request parameters

Send multipart/form-data. Supplying any of reference_video/reference_video_url/reference_image/reference_image_url is what selects this mode — there’s no separate source parameter. Supplying none of the four does not error; see the warning above — the request is generated as text-to-video instead.

Reference video vs. reference images

You can supply a reference video, one or more reference images, or both together in the same request — a reference video is not required if you supply at least one reference image, and vice versa.
  • Reference video (reference_video / reference_video_url): both fields are declared as arrays for forward compatibility, but at most 1 reference video is accepted today across the two combined — supplying more (two files, two URLs, or one of each) answers 400 INVALID_REQUEST — “at most 1 reference video(s) allowed”. The reference video itself must be 0.5–600 seconds long and at least 64x64 with even width and height — the same upload constraints enforced elsewhere in this API. This is independent of duration_s, which controls the duration of the generated output video, not the reference.
  • Reference images (reference_image / reference_image_url): each can be repeated and the two forms can be freely mixed, but the combined count across both cannot exceed 4. Going over answers 400 INVALID_REQUEST — “at most 4 reference images are allowed”.
Reference fields cannot be combined with first_frame_image/last_frame_image (file or URL form). Supplying both answers 400 INVALID_REQUEST — “reference_video/reference_image cannot be combined with first_frame_image/last_frame_image”.

Response parameters

Returns 200 OK — an acceptance acknowledgment, not the final result.
This response deliberately carries none of the fields GET /v1/videos/{video_id} returns (stage, video_url, alpha_url, completed_at, error). See Get Video for the full shape once the video is processing or done.

Examples

@viggle/sdk

Common errors

Next step

Use Get Video with the returned id to poll for the result.

Generate Video (from Text)

Generate from a prompt alone, with no frame image or reference.

Generate Video (from First Frame and/or Text)

Anchor only the start of the video, with no last frame.

Generate Video (from First-Last Frames and/or Text)

Also anchor the end of the video on a last frame.

Generate Video (from Character Animation)

Apply a driving video’s motion and/or character images on a separate backend.

Authorizations

Authorization
string
header
required

Server-side SDK clients use a project API key. Remote MCP clients use an OAuth access token. Never expose a project API key in browser code.

Headers

X-Request-Id
string

Optional caller-supplied correlation ID, up to 128 characters. The service returns the effective value in the response header for tracing and support.

Required string length: 1 - 128
X-Viggle-Source
string

Optional source-channel label, up to 128 characters, used to attribute traffic to an SDK, integration, product surface, or internal workflow.

Required string length: 1 - 128

Body

multipart/form-data

Body of POST /v1/videos, multipart/form-data only (character- animation mode below also accepts a plain application/json body — see Generate Video (from Character Animation)). Which fields are supplied selects the generation mode:

  • Neither first_frame_image/first_frame_image_url nor last_frame_image/last_frame_image_url nor any reference or character-animation field supplied: text-to-video.
  • A first frame supplied, no last frame: first-frame-to-video.
  • Both a first frame and a last frame supplied: first+last-frame-to-video.
  • Any of reference_video/reference_video_url/ reference_image/reference_image_url supplied: reference-video (omni-reference) generation.
  • driving_video_url and/or character_image_url/ character_image_urls supplied: character-animation generation, dispatched to a separate backend from the four modes above. It has no quality tier, no duration_s/resolution/ aspect_ratio/seed, and prompt is optional rather than required; see below and Generate Video (from Character Animation) for its own fields, pricing, and constraints.

Within a frame slot, supply at most one of the file and the URL form. Supplying both first_frame_image and first_frame_image_url (or both last_frame_image and last_frame_image_url) answers 400 INVALID_REQUEST with "supply only one of first_frame_image or first_frame_image_url" (or the last_frame_* equivalent). A last frame requires a first frame; supplying a last frame with no first frame answers 400 INVALID_REQUEST with "a last frame requires a first frame".

Reference-video mode is selected purely by whether any of the four reference fields is present — there is no separate source/mode parameter, and no error if you meant to but forgot: supplying none of reference_video/reference_video_url/reference_image/ reference_image_url simply generates text-to-video instead (the first bullet above), the same way omitting first_frame_image/ last_frame_image falls back to text-to-video rather than erroring. reference_video and reference_video_url are declared as arrays for forward compatibility, but at most 1 reference video is accepted today; supplying any combination of the two fields that adds up to more than 1 (two files, two URLs, or one of each) answers 400 INVALID_REQUEST with "at most 1 reference video(s) allowed". reference_image and reference_image_url may be mixed freely, but their combined count cannot exceed 4; going over answers 400 INVALID_REQUEST with "at most 4 reference images are allowed". Reference fields cannot be combined with first_frame_image/last_frame_image (file or URL form); doing so answers 400 INVALID_REQUEST with "reference_video/reference_image cannot be combined with first_frame_image/last_frame_image". The reference video itself (independent of duration_s, the target duration of the generated video) must be 0.5–600 seconds long and at least 64x64 with even width and height, the same constraints enforced on uploaded video elsewhere in this API.

Character-animation mode cannot be combined with quality (or any frame/reference field above) — doing so answers 400 INVALID_REQUEST with "driving_video_url/character_image_url cannot be combined with quality". At least one character image is required (character_image_url and character_image_urls are mutually exclusive ways to supply them — "supply only one of character_image_url or character_image_urls" otherwise); up to 4 are accepted when driving_video_url is absent, but only 1 when it's present ("only one character_image_url is allowed when driving_video_url is provided"). driving_video_url itself is optional, single-valued, and — unlike every other video input in this API — checked against a narrower 5–10 second (inclusive) duration window rather than 0.5–600 seconds, on top of the same at-least-64x64/even-dimensions checks.

Billed at ⌈duration_s⌉ × the per-second credit rate for quality (currently 1 credit/second — $0.01/sec — for both low and high). resolution and aspect_ratio do not affect price, and image/video-conditioned generation (first-frame, first-last-frame, or reference-video) costs the same as text-only for the same quality and duration. Character-animation mode is billed differently — a flat rate regardless of actual output duration; see Generate Video (from Character Animation).

Every generated video includes native audio; there is no separate audio flag or field.

prompt
string

Text description of the desired video. Required and non-empty for text, first-frame, first+last-frame, and reference-video modes. Optional (and merely a style/content hint, not enforced non-empty) for character-animation mode.

Minimum string length: 1
Example:

"A paper airplane gliding through a sunlit office"

quality
enum<string>

Generation quality tier — also selects the per-second credit rate charged for this request. low generates faster, for quicker iteration; high generates slower but produces higher-fidelity output. Both tiers are billed at the same $0.01/sec rate. Required for every mode except character-animation, which has no quality tiers and rejects this field outright if supplied.

Available options:
low,
high
Example:

"low"

first_frame_image
file

First-frame image uploaded directly. Mutually exclusive with first_frame_image_url. Supplying either switches on first-frame-to-video mode. Cannot be combined with any reference_video/reference_image field.

first_frame_image_url
string<uri>

Publicly reachable URL of the first-frame image; the service fetches and re-hosts it. Mutually exclusive with first_frame_image. Cannot be combined with any reference_video/reference_image field.

last_frame_image
file

Last-frame image uploaded directly. Mutually exclusive with last_frame_image_url. Valid only alongside a first frame. Cannot be combined with any reference_video/reference_image field.

last_frame_image_url
string<uri>

Publicly reachable URL of the last-frame image; the service fetches and re-hosts it. Mutually exclusive with last_frame_image. Valid only alongside a first frame. Cannot be combined with any reference_video/reference_image field.

reference_video
file[]

Reference video uploaded directly, for reference-video (omni-reference) generation. Declared as an array for forward compatibility, but at most 1 is accepted today — combined with reference_video_url. Not required if at least one reference image is supplied instead. Must be 0.5–600 seconds long and at least 64x64 with even width/height. Cannot be combined with first_frame_image/last_frame_image.

Maximum array length: 1
reference_video_url
string<uri>[]

Publicly reachable URL of the reference video; the service fetches and re-hosts it. Declared as an array for forward compatibility, but at most 1 is accepted today — combined with reference_video. Same duration/resolution constraints as reference_video.

Maximum array length: 1
reference_image
file[]

Reference images uploaded directly, for reference-video (omni-reference) generation. Up to 4 total, combined with reference_image_url. Can be freely mixed with reference_image_url.

Maximum array length: 4
reference_image_url
string<uri>[]

Publicly reachable URLs of reference images; the service fetches and re-hosts each one. Up to 4 total, combined with reference_image. Can be freely mixed with reference_image.

Maximum array length: 4
driving_video_url
string<uri>

Publicly reachable URL (https://) or internal gs:// object of a driving video, for character-animation generation — its motion is applied to the character image(s). Optional and single-valued; a character-animation request can run on character images alone. Must be 5–10 seconds long (inclusive), at least 64x64, and even width/height. Selects character-animation mode together with any character_image_url/character_image_urls; cannot be combined with quality or any frame/reference field above.

character_image_url
string<uri>[]

Character reference image URL(s) (https:// or gs://), repeatable, for character-animation generation. Mutually exclusive with character_image_urls — supply one field or the other, not both. At least one character image is required across the two fields; up to 4 total when driving_video_url is absent, but only 1 when it's present.

character_image_urls
string<uri>[]

Same as character_image_url, supplied as one field instead of repeated ones — as a JSON array of strings on a multipart request, or natively on a JSON request body. Mutually exclusive with character_image_url.

priority
integer
default:1000

Admission-queue priority tier, shared by H3 and character-animation modes. Defaults to 1000 (top tier) — most callers never need to set this. Must be one of the server's configured tiers (currently 1000 or 0); an unsupported value answers 400 INVALID_REQUEST with "unsupported priority".

duration_s
number
default:5

Target video duration in seconds.

Required range: 3 <= x <= 15
resolution
enum<string>
default:768p

Output resolution tier.

Available options:
480p,
768p,
1080p
aspect_ratio
enum<string>
default:16:9

Output aspect ratio.

Available options:
16:9,
9:16,
1:1,
4:3,
3:4,
21:9
seed
integer

Deterministic generation seed. Omit for a random seed. H3 modes only — not applicable to character-animation mode.

Required range: x >= 0
watermark
boolean
default:false

Whether to burn in a Viggle watermark.

Response

Video generation accepted and queued.

Acceptance acknowledgment for POST /v1/videos, shared by all five generation modes. This is a queued confirmation, not the final result — poll GET /v1/videos/{video_id} (or watch it via GET /v1/videos) until status reaches ready, then read video_url from that response.

id
string
required

Public video ID — vid_-prefixed for the four H3 modes, anim_-prefixed for character-animation mode.

Minimum string length: 1
status
enum<string>
required

Lifecycle state at acceptance time; always queued.

Available options:
queued,
processing,
ready,
failed,
cancelled
progress
integer | null
required

Always null on acceptance.

Required range: 0 <= x <= 100
created_at
string<date-time> | null
required

ISO 8601 creation timestamp, second precision.