Seedance 2.5 Flash Text to Video API
seedance-2.5-flash/text-to-videoSeedance 2.5 Flash Text to Video turns text prompts into 4–30 second videos with synchronized audio, auto or six fixed aspect ratios, and 480p or 720p output. It follows the action order, camera moves, and sound cues you write, keeping characters and settings coherent across the clip.
Input
Output
ReadyContinue with
REST API
Quick Start
Authenticate, submit a valid input object, then use task_id to retrieve the video.
Connect to the Vidgo API
Create an API key, keep it only on your server, and send Authorization: Bearer VIDGO_API_KEY.
- Endpoint
- POST
https://api.vidgo.ai/api/generate/submit - Authentication
- Authorization: Bearer VIDGO_API_KEY
Submit one generation task
Run the smallest valid payload for this workflow. A successful submission immediately returns task_id without waiting for the video.
REQUEST_BODY=$(cat <<'JSON'
{
"model": "seedance-2.5-flash/text-to-video",
"input": {
"prompt": "A tracking shot follows a cyclist through a rain-lit night market.",
"duration": 5,
"resolution": "720p",
"aspect_ratio": "16:9",
"generate_audio": true
}
}
JSON
)
RESPONSE=$(curl --silent --show-error --fail-with-body \
--request POST \
--url "https://api.vidgo.ai/api/generate/submit" \
--header "Authorization: Bearer $VIDGO_API_KEY" \
--header "Content-Type: application/json" \
--data "$REQUEST_BODY")
CODE=$(printf '%s' "$RESPONSE" | jq -r '.code // empty')
if [ "$CODE" != "0" ] && [ "$CODE" != "200" ]; then
printf 'API error: %s
' "$RESPONSE" >&2
exit 1
fi
printf '%s
' "$RESPONSE"Wait for the result
Query with task_id, continue for not_started/running, and stop for finished/failed. On success, read data.files[].file_url.
Track status
GET https://api.vidgo.ai/api/generate/status/{task_id}Poll about every 2 seconds, then back off gradually. Continue only for not_started or running and stop on finished or failed. You can instead add callback_url to the same top-level request contract.
not_startedrunningfinishedfailed{
"code": 200,
"data": {
"task_id": "task-unified-...",
"status": "running",
"created_time": "2026-08-22T10:00:00Z"
}
}{
"code": 200,
"data": {
"task_id": "task-unified-...",
"status": "finished",
"files": [
{
"file_url": "https://storage.vidgo.ai/generated/video.mp4",
"file_type": "video"
}
],
"created_time": "2026-08-22T10:00:00Z",
"progress": 100,
"error_message": null
}
}Complete runnable example
Expand for a complete script with HTTP and business-code checks, task_id validation, polling, terminal-state handling, and a timeout boundary.
set -euo pipefail
: "${VIDGO_API_KEY:?Set VIDGO_API_KEY in your environment}"
REQUEST_BODY=$(cat <<'JSON'
{
"model": "seedance-2.5-flash/text-to-video",
"input": {
"prompt": "A tracking shot follows a cyclist through a rain-lit night market.",
"duration": 5,
"resolution": "720p",
"aspect_ratio": "16:9",
"generate_audio": true
}
}
JSON
)
SUBMIT_RESPONSE=$(curl --silent --show-error --fail-with-body \
--request POST \
--url "https://api.vidgo.ai/api/generate/submit" \
--header "Authorization: Bearer $VIDGO_API_KEY" \
--header "Content-Type: application/json" \
--data "$REQUEST_BODY")
TASK_ID=$(printf '%s' "$SUBMIT_RESPONSE" | jq -r '.data.task_id // .task_id // empty')
BUSINESS_CODE=$(printf '%s' "$SUBMIT_RESPONSE" | jq -r '.code // empty')
if [ "$BUSINESS_CODE" != "0" ] && [ "$BUSINESS_CODE" != "200" ]; then
printf 'Submit failed:
%s
' "$SUBMIT_RESPONSE" >&2
exit 1
fi
if [ -z "$TASK_ID" ]; then
printf 'Submit response did not include task_id:
%s
' "$SUBMIT_RESPONSE" >&2
exit 1
fi
START_TIME=$(date +%s)
POLL_DELAY=2
while true; do
if [ $(( $(date +%s) - START_TIME )) -ge 600 ]; then
printf 'Timed out after 600 seconds
' >&2
exit 1
fi
STATUS_RESPONSE=$(curl --silent --show-error --fail-with-body \
--url "https://api.vidgo.ai/api/generate/status/$TASK_ID" \
--header "Authorization: Bearer $VIDGO_API_KEY")
STATUS=$(printf '%s' "$STATUS_RESPONSE" | jq -r '.data.status // .status // empty')
BUSINESS_CODE=$(printf '%s' "$STATUS_RESPONSE" | jq -r '.code // empty')
if [ "$BUSINESS_CODE" != "0" ] && [ "$BUSINESS_CODE" != "200" ]; then
printf 'Status request failed:
%s
' "$STATUS_RESPONSE" >&2
exit 1
fi
case "$STATUS" in
finished)
printf '%s' "$STATUS_RESPONSE" | jq -r '(.data.files // .files // [])[]?.file_url'
break
;;
failed)
printf '%s' "$STATUS_RESPONSE" | jq -r '.data.error_message // .error_message // "Generation failed"' >&2
exit 1
;;
not_started|running)
sleep "$POLL_DELAY"
if [ "$POLL_DELAY" -lt 10 ]; then POLL_DELAY=$((POLL_DELAY + 1)); fi
;;
*)
printf 'Unexpected task status: %s
' "$STATUS" >&2
exit 1
;;
esac
doneInput parameters
These are the fields accepted inside input. The request example shows the required top-level model field.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| prompt | string | Yes | — | Text prompt describing the video. |
| duration | integer | Yes | — | An integer from 4 through 30, inclusive. |
| resolution | string | No | 720p | 480p or 720p. |
| aspect_ratio | string | No | — | auto, 21:9, 16:9, 4:3, 1:1, 3:4, or 9:16. |
| generate_audio | boolean | No | — | Whether to generate synchronized audio; the rate is the same either way. |
Response Fields
Submission returns task identity immediately. Status responses add progress, every output file, or a failure message.
| Field | Type | Description |
|---|---|---|
| code | integer | Application result code; successful responses use 0 or 200. |
| message | string | Human-readable message or error detail when present. |
| data.task_id | string | Task ID used in the status endpoint path. |
| data.status | string | not_started, running, finished, or failed. |
| data.created_time | string | Task creation time in date-time format. |
| data.progress | integer | 0–100 progress when reported by the provider. |
| data.files[] | array | All output files from a successful task, in response order. |
| data.files[].file_url | string | Public URL for a generated video. |
| data.files[].file_type | string | File type, such as video. |
| data.error_message | string | null | Failure detail when status is failed. |
Task Lifecycle
Treat not_started and running as non-terminal states. finished and failed are terminal alternatives; stop polling when either is returned.
not_startedThe task was accepted and is waiting to begin.
runningGeneration is in progress. Continue polling the same task_id.
finishedGeneration succeeded. Read every video URL from data.files[].file_url.
failedGeneration stopped with an error. Read data.error_message and stop polling.
Polling and Errors
- AuthenticationA 401 response means the Bearer API key is missing or invalid. Correct it before retrying.
- ValidationA 400 response identifies an invalid field, unsupported media key, or insufficient credit balance. Correct the request before resubmitting.
- Network and timeoutA transport failure is different from a failed task. Retry status checks with a bounded timeout before deciding that the task failed.
- Polling intervalStart around every 2 seconds and increase the interval gradually for a long-running task.
- Terminal statesContinue only for not_started or running. Stop immediately on finished or failed.
- Callback optionProvide callback_url at the request top level to receive the final flat task object; polling remains available if delivery fails.
Endpoint limits
| Specification | Value | Details |
|---|---|---|
| Input mode | Text prompt | A prompt defines the scene, action, camera direction, and sound. |
| Output | Video task | The endpoint returns an asynchronous task ID; the video can include synchronized audio. |
| Resolution | 480p / 720p | Defaults to 720p. |
| Duration | 4–30 seconds | Every whole-second value in the inclusive range. |
| Aspect ratio | Auto + 6 fixed | auto, 21:9, 16:9, 4:3, 1:1, 3:4, 9:16. |
| Billing basis | Output seconds | 480p uses 18.5 credits/s; 720p uses 41 credits/s. |
Related Models
Seedance 2.5 Flash Text to Video API frequently asked questions
What is the Seedance 2.5 Flash Text to Video API?
Seedance 2.5 Flash Text to Video is a ByteDance Seed model for generating video from text prompts. It creates 4–30 second clips at 480p or 720p with optional synchronized audio, auto framing, and six fixed aspect ratios, at about a third less per second than Seedance 2.5. Built on the Seedance 2.5 multimodal audio-video workflow, it follows the action order, camera direction, and sound described in the prompt while keeping characters and settings coherent. You can call it programmatically or try it from the playground above.
How does Seedance 2.5 Flash Text to Video compare with Seedance 2.5?
Both endpoints accept the same input fields and generate 4–30 second clips with optional synchronized audio. Flash outputs 480p or 720p at 18.5 and 41 credits per second, while Seedance 2.5 Text to Video costs 28 and 63 credits per second and adds 1080p. Draft and publish at 720p on Flash, and switch the model ID to Seedance 2.5 when a shot needs 1080p.
Can Seedance 2.5 Flash Text to Video generate a 30-second clip?
Yes. Set duration to any whole number from 4 to 30 seconds. Billing follows the output length, so a 30-second clip at 720p costs 1,230 credits ($6.15). Describe the beats in order so a longer clip develops clearly from start to finish.
How many credits per second does Seedance 2.5 Flash Text to Video use?
480p uses 18.5 credits per output second ($0.0925) and 720p uses 41 ($0.205). A 5-second 720p clip costs 205 credits, and audio on or off uses the same rate. The Run button in the playground shows the exact price before you submit.
Does Seedance 2.5 Flash Text to Video generate synchronized audio?
Yes. Set generate_audio to true and the video comes with sound generated in the same pass, such as ambience, effects, and dialogue. Name the sources you want in the prompt for clearer results. Setting it to false returns a silent video at the same price.
Which aspect ratios does Seedance 2.5 Flash Text to Video support?
Choose auto or one of six fixed ratios: 21:9, 16:9, 4:3, 1:1, 3:4, and 9:16. Use 9:16 for vertical social video, 16:9 or 21:9 for widescreen scenes, and 1:1 for square feeds.
How should I structure a Seedance 2.5 Flash Text to Video prompt?
Write the subject and setting first, then the action in order, then camera direction, lighting, and sound. Keep camera movement in its own sentence and use words such as first, then, and finally for multi-beat clips. Iterating at 480p is a cost-efficient way to settle timing before the 720p pass.
When should I use Seedance 2.5 Flash Image to Video instead of Text to Video?
Choose Seedance 2.5 Flash Image to Video when you already have the opening frame, such as a product shot or character design, and want the video to start from it. Stay with Text to Video when the whole scene can be described in words.















