Seedance

Overview

This registered video queue requires a deployment bound to its Fal transport. A Seedance model using content-generation transport cannot be called through Fal.

Endpoint and authentication

POST /queue/bytedance/seedance-2.0/text-to-video

Use an XHub API key: Authorization: Bearer . Do not use upstream provider credentials as gateway keys.

Use the gateway root Base URL shown in the playground, without appending /v1; send requests to the full endpoint path above.

Request example

curl "$XHUB_BASE_URL/queue/bytedance/seedance-2.0/text-to-video" \
  -H "Authorization: Bearer $XHUB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"A lighthouse at sunrise.","duration":5}'

Request parameters

Success response

{
  "request_id": "request-example"
}

Errors and troubleshooting

Task lifecycle

curl "$XHUB_BASE_URL/queue/bytedance/seedance-2.0/requests/$REQUEST_ID/status" -H "Authorization: Bearer $XHUB_API_KEY"
curl "$XHUB_BASE_URL/queue/bytedance/seedance-2.0/requests/$REQUEST_ID" -H "Authorization: Bearer $XHUB_API_KEY"

Save request_id as REQUEST_ID, poll status until completion, then retrieve the result. Prefer returned status_url and response_url resolved against the gateway root. Use the same XHub key. Cancellation is not implemented. Successful terminal results with measured usage settle once.

Registered creation paths

Image/reference fields follow deployment endpoint details. Fast/Mini share the version query queue; do not append /requests to a creation URL. For byteplus use /queue/byteplus/seedance-{version}/requests/{request_id}. Optional model selects a public alias and is removed before forwarding.