Seedance 2.0

Generate a video asynchronously with Seedance 2.0 through the 国际即梦 channel. Submit a task, poll its status, then download the completed MP4 from LEAPERone.

Discover with the CLI

The CLI and website expose the same documentation page. Reading docs is public; endpoints requires auth login or LEAPERONE_API_KEY.

npx @leaperone/cli@latest endpoints
npx @leaperone/cli@latest docs read api-reference/video-generation

Create a task

curl -X POST https://api.leaper.one/v1/videos \
  -H "Authorization: Bearer sk-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "seedance-2.0",
    "prompt": "A cinematic 9:16 video of a cat running through warm sunlight.",
    "seconds": 15,
    "aspect_ratio": "9:16"
  }'

{
  "id": "video_01234567-89ab-cdef-0123-456789abcdef",
  "object": "video",
  "model": "seedance-2.0",
  "status": "queued",
  "progress": 0
}

Parameters

Local file paths cannot be used in JSON. Upload references to a public URL first, or provide supported images as base64 data URLs.

Use a CDN image reference

Seedance downloads reference images from the URL in images. Before submitting the task, make sure the CDN URL:

• returns 200 to an unauthenticated GET request;
• returns an image Content-Type such as image/png, image/jpeg, or image/webp;
• does not require cookies, a browser session, or request headers that Seedance cannot send;
• remains valid until generation finishes. For signed URLs, use an expiry of at least 30 minutes.

Verify the image first:

export IMAGE_URL="https://cdn.example.com/reference.png"
curl -fsSL -o /dev/null -D - "$IMAGE_URL"

Then submit an image-to-video task:

The complete shell example uses curl and jq.

export LEAPERONE_API_KEY="sk-your-api-key"

CREATE_RESPONSE=$(curl -sS --fail-with-body https://api.leaper.one/v1/videos \
  -H "Authorization: Bearer $LEAPERONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --arg image "$IMAGE_URL" '{
    model: "seedance-2.0",
    prompt: "Add subtle natural motion and a slow cinematic camera push-in. Preserve the original composition.",
    seconds: 5,
    aspect_ratio: "16:9",
    images: [$image]
  }')")

echo "$CREATE_RESPONSE"
VIDEO_ID=$(printf '%s' "$CREATE_RESPONSE" | jq -er '.id')

Poll every 10 seconds until the task reaches a terminal state:

for attempt in $(seq 1 180); do
  STATUS_RESPONSE=$(curl -sS --fail-with-body \
    "https://api.leaper.one/v1/videos/$VIDEO_ID" \
    -H "Authorization: Bearer $LEAPERONE_API_KEY")
  echo "$STATUS_RESPONSE"

  STATUS=$(printf '%s' "$STATUS_RESPONSE" | jq -r '.status')
  case "$STATUS" in
    completed) break ;;
    failed|cancelled) exit 1 ;;
  esac

  sleep 10
done

[ "$STATUS" = "completed" ] || exit 1

Download the completed video:

curl -fL "https://api.leaper.one/v1/videos/$VIDEO_ID/content" \
  -H "Authorization: Bearer $LEAPERONE_API_KEY" \
  -o result.mp4

If a task returns failed, change the reference image or prompt and create a new task. Common causes include an expired or protected CDN URL and content moderation. Failed and cancelled tasks are not charged.

Poll status

curl https://api.leaper.one/v1/videos/video_01234567-89ab-cdef-0123-456789abcdef \
  -H "Authorization: Bearer sk-your-api-key"

Status values include queued, processing, completed, failed, and cancelled.

Download content

curl -L https://api.leaper.one/v1/videos/video_01234567-89ab-cdef-0123-456789abcdef/content \
  -H "Authorization: Bearer sk-your-api-key" \
  -o result.mp4

Billing and logs

• Credits are reserved when the task is submitted.
• Each successful video task costs 1 credit ($1.00), whether it requests 5, 10, or 15 seconds. CNY top-ups use the platform's fixed exchange rate and may include channel fees.
• The charge is settled only when the task reaches completed.
• Failed and cancelled tasks release the reserved credits.
• Usage history records the request ID, API key, public model, duration, channel, and final charge.
• Every response includes X-Request-Id; keep it when contacting support.
• Prompts, reference media contents, upstream task IDs, upstream URLs, and credentials are not exposed in API responses or usage logs.
• Task IDs are scoped to the owning LEAPERone account. Other users receive 404.