Submit Task (Doubao / Seedance Format)
Doubao video models (the Seedance series, e.g. seedance-1-0-pro-250528, doubao-seedance-2-0-260128, doubao-seedance-2-0-mini-260615 — see the Model Plaza) reuse the generic task format's endpoint — no separate integration needed (for the request structure overview see Create Video Generation Task). This page documents the Doubao channel's parameter mapping and channel differences; for querying see Query & Download.
Endpoint
Creation and query reuse the generic task format endpoints: POST /v1/video/generations and GET /v1/video/generations/{task_id}.
Request Body
The gateway converts the request into the upstream's {model, content[], ...parameters} structure and forwards it: prompt becomes the text item in the upstream content array; image / images become image items. All other generation parameters are passed through metadata and merged into the upstream request body by field name (unrecognized keys are dropped).
Top-level duration, size, mode, width, height, fps, seed, n, response_format, user are silently dropped on the Doubao channel (no error, no effect): use seconds for duration, and metadata.ratio + metadata.resolution for the frame. Verified by test: the same request with top-level duration: 8 + seconds: "5" produced a 5-second video; top-level seed: 999 + metadata.seed: 42 echoed 42.
The upstream validates parameters per "model × mode": unsupported combinations return 400 at submission (the message carries the model name, the mode, and a Request id) — just remove the offending parameter and retry. Tested (2026-09):
doubao-seedance-2-0-260128t2v:resolution/ratio/seed/duration/generate_audio/return_last_frame/watermark/camera_fixedall take effect (1080p output and audio track verified;camera_fixedre-tested 2026-10 — t2v submission returns 200 andtrue/falseshow clearly different camera movement);frames/service_tierare not supporteddoubao-seedance-2-0-mini-260615i2v:ratio/generate_audiotake effect (720p output with audio track);resolutionis not supported — when omitted the output is fixed at 720p- Text-to-video frame rate is fixed at 24fps across models; other "model × mode" combinations are untested — defer to upstream errors
Image-to-video (i2v) image / images do not accept photos of real people: The upstream compliance check rejects them outright with 400 InputImageSensitiveContentDetected.PrivacyInformation (no task created, no billing). Use illustration / anime / product / scenery images for the first frame.
Request Examples
Response Body
A successful submission returns a task object; the task_id is used for querying, and status starts as queued.
Response Example
For status query and download see Query & Download.
