Overview
Seedance 2.5 is a video generation model for prompt-only video, first-and-last-frame animation, and multimodal reference workflows. Use this page when you need up to 30-second video generation with optional image, video, or audio references, or when you want to review low-cost 480p Drafts before producing selected results in 1080p.Endpoint and authentication
Base URL:
All requests require your APIXO API key:
Recommended: Draft first, Final second
Step 1: Generate a 480p Draft
Setinput.draft=true. resolution may be omitted because Draft generation is fixed to 480p.
state=success. Keep this APIXO task ID; it is the value used as draft_task_id in the next step.
Step 2: Generate the 1080p Final
Send the successful Draft task ID.resolution may be omitted because Final generation is fixed to 1080p.
prompt, reference media, mode, duration, aspect_ratio, or sound. A successful Draft can be reused to create multiple independent Finals for 7 days. Each Final returns its own task ID and is charged to the API key that submits that Final request.
Why this workflow saves about 57%
For a no-video-reference workflow that compares four candidates of the same duration:Copy-paste async quickstart
This minimal request submits a text-to-video task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Request body
Text-to-video
Dynamic duration
Useduration=-1 when you want the generation system to decide the final output length.
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.5 input parameters.
Draft and Final input rules
For Final requests, generation fields such as
prompt, reference URLs, mode, duration, aspect_ratio, sound, and nsfw_checker are inherited from the Draft and must not be resent. draft=true and draft_task_id are mutually exclusive.
Video-editing prompt behavior
Seedance 2.5 can infer a video-editing task from the prompt text. If your prompt asks the model to edit, add, remove, modify, replace, or change parts of an existing video, send the request with:mode is still omni_reference. Examples of prompt terms that can trigger this behavior include edit video, add, add to, delete, remove, modify, replace, change to, 编辑视频, 增加, 加上, 删除, 去掉, 修改, 替换, and 改成.
Response format
Submit task response
POST /generateTask/seedance-2-5 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. Present only on successful terminal responses for
seedance-2-5 tasks submitted with duration=-1.string
Settlement status. For this final snapshot the value is always
final.number
Total duration of all input videos, in seconds, rounded half up to 3 decimal places.
number
Actual generated output video duration, in seconds, rounded half up to 3 decimal places.
number
Final billable duration in seconds. For this model, this is always
inputVideoSeconds + outputVideoSeconds.string
Duration unit. The value is
second.string
Rounding rule used for duration fields. The value is
round half up to 3 decimal places.integer
Number of input videos included in
inputVideoSeconds.integer
Number of output videos included in
outputVideoSeconds.Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.code, message, and data. Successful callbacks include the final state and resultJson. For duration=-1 tasks, successful terminal callbacks include the same data.billing object returned by status polling. See Webhooks for delivery requirements and retry behavior.
Billing
Seedance 2.5 is billed per second. The selectedresolution and whether omni_reference includes video_urls determine the per-second unit price.
Formula without 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.
When duration=-1, APIXO pre-charges the output portion as 30 seconds. After a successful task, APIXO settles by the actual generated output duration and refunds any overcharged output seconds. If video_urls are provided, reference video seconds are still included in billable seconds.
When the source Draft uses duration=-1, APIXO uses its final actual output duration for the 1080p Final, rounded half up to 3 decimal places. For example, a Draft settled at 10.080 seconds uses 10.080 output seconds when calculating the Final pre-charge. If the Draft used video references, the original total reference-video duration is added to the actual output duration before applying the 1080p video-reference rate.
Successful terminal duration=-1 responses return the final settled seconds under data.billing:
billing use seconds and are rounded half up to 3 decimal places. inputVideoSeconds is the sum of all input video durations, and inputVideoCount is the number of input videos included in that sum. outputVideoSeconds is the actual generated output duration. totalBillableSeconds is always inputVideoSeconds + outputVideoSeconds. This billing object appears only after successful final settlement, is also included in successful callback payloads, and remains stable on repeated polling.
For current route and market comparison pricing, see Pricing.
Latency and polling
Seedance 2.5 tasks are asynchronous. Actual latency may vary by prompt complexity, duration mode, resolution, reference media accessibility, route queue load, and storage transfer time.
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 is generated from APIXO’s mapped generation error. Common values include:
See Error Codes for the full error reference.