Skip to main content

Overview

Seedance 2.0 is a ByteDance video generation model for prompt-only video, first-and-last-frame animation, and multimodal reference workflows. Use this page when you are ready to call the API after trying the model in the APIXO playground.

Endpoint and authentication

Base URL:
All requests require your APIXO API key:
Submit requests also require:

Copy-paste async quickstart

This minimal request submits a text-to-video task and returns a taskId.
Successful response:
Save the taskId; you need it to poll for the final result.

Poll for result

Processing response:
Success response:
Failed response:
Parse resultJson after state becomes success:

Request body

Text-to-video

First-and-last-frames

Omni-reference

Parameters

string
default:"async"
Result delivery mode. Omit this field or use async for polling with statusTask, or use callback for webhook delivery.
string
Required when request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.
object
required
Seedance 2.0 input parameters.
In omni_reference, audio-only requests are rejected. If you provide audio_urls, include at least one image or video reference as well.
Use public, directly accessible URLs for all reference media. Video and audio durations are checked before the task is submitted.
image_urls examples use URL strings. The backend also accepts object items with a non-empty url field and normalizes them to URL strings.

Response format

Submit task response

POST /generateTask/seedance-2-0 returns a task ID when the task is accepted:
integer
API status code. 200 means the task was accepted.
string
Human-readable status message.
string
Unique task identifier used with the status endpoint.

Status response fields

string
Unique task identifier.
string
Current task state: pending, processing, success, or failed.
string
JSON string containing generated video URLs in resultUrls. Present when state is success.
string
Machine-readable failure code. Present when state is failed.
string
Human-readable failure message. Present when state is failed.
integer
Task creation timestamp in Unix milliseconds.
integer
Task completion timestamp in Unix milliseconds. Present after completion.
integer
Processing duration in milliseconds. Present after completion when timing data is available.
object
Final billing snapshot under data.billing, returned on successful terminal status and callback responses for new tasks. Older tasks may omit this object; see Billing for compatibility rules.
string
Settlement status. The final snapshot uses final.
string
Opaque identifier of the billing rule captured when this task was created. Do not infer the rule from polling time.
number
Actual total reference-video duration in seconds. Zero without video references; this is not raised to the minimum billable input.
number
For new tasks with video references, ceil(outputVideoSeconds * 2 / 3), rounded upward to a whole second. Zero without video references or under the original rule.
number
The larger of inputVideoSeconds and minimumInputVideoSeconds; zero without video references.
number
Output duration used for billing, in seconds.
number
Total billed seconds: outputVideoSeconds + billableInputVideoSeconds.
string
Duration unit. The value is second.

Webhook callback mode

Use callback mode when your backend should receive the final result automatically instead of polling.
The callback payload uses the same top-level shape as status polling with code, message, and data. Successful callbacks include the final state and resultJson. Successful terminal callbacks for new tasks also include data.billing. See Webhooks for delivery requirements and retry behavior.

Billing

Seedance 2.0 is billed per second. The selected resolution and whether omni_reference includes video_urls determine the per-second unit price. Formula without video reference:
Formula with video reference:
text-to-video and first_and_last_frames always use the without-video-reference rate. omni_reference uses the with-video-reference rate only when video_urls is provided. Image and audio references do not add extra billable seconds. ceil rounds upward to the next whole second. The minimum applies once to the total reference-video duration, not separately to each video. For example, 5 output seconds with 3 actual reference seconds bills 5 + max(3, 4) = 9 seconds; 6 output seconds with 2 actual reference seconds bills 10 seconds. This rule applies to tasks created after the billing update. Existing tasks retain the rule captured at creation: with video references, (output duration + actual total reference video duration) * unit price; without video references, output duration only. Per-second prices, custom prices, and user discounts are unchanged. Polling or receiving a callback after the update does not change an existing task’s rule. Successful terminal status and callback responses for new tasks include data.billing. Duration values use seconds with three decimal places; minimumInputVideoSeconds is a whole-second ceiling. inputVideoSeconds remains the actual input duration, while billableInputVideoSeconds is the charged input duration. The snapshot remains stable on repeated polling. Older tasks may omit billing or the new fields; clients must not require them for historical tasks. For example, the billing snapshot for 5 output seconds with 3 reference-video seconds includes:
For current route and market comparison pricing, see Pricing.

Latency and polling

Video generation is long-running. The user manual lists typical Seedance 2.0 generation time at about 4-8 minutes. Actual latency may vary by prompt complexity, duration, resolution, reference media accessibility, route queue load, and storage transfer time.
For production workloads, use callback mode to avoid frequent polling while video tasks run.
Result URLs are temporary. Download and store important outputs promptly after task completion. Rate limits and concurrency can vary by account, API key, and route. If you receive 429, slow down requests and retry with backoff. For account-level details, see System APIs.

Errors and troubleshooting

HTTP errors

Validation notes

Task failure codes

failCode identifies the task failure. Common values include: See Error Codes for the full error reference.