Light Speed Future

DOCUMENTATION

Generate your first video

On this page

Native Seedance 2.5 · 5 seconds · 720p · 16:9 · MP4 without audio

Use macOS or Linux Terminal with curl. This example uses your LSF test balance.

1 Paste your account details

Replace both values with the API key and exact model alias in your welcome message. Paste into Terminal and press Enter.

export LSF_KEY='PASTE_YOUR_API_KEY'
export LSF_MODEL='PASTE_YOUR_NATIVE_2_5_ALIAS'

2 Create the video once

Paste this entire block into the same Terminal window and press Enter.

curl -sS 'https://ai-api.lightspeedfuture.com/v1/videos' \
  -H "Authorization: Bearer $LSF_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary @- <<JSON
{
  "model": "$LSF_MODEL",
  "prompt": "Ocean waves at sunset.",
  "metadata": {
    "duration": 5, "resolution": "720p", "ratio": "16:9",
    "output_format": "mp4", "generate_audio": false
  }
}
JSON

The response contains task_id, such as task_abc123. Copy that value for step 3. If no task ID is returned, contact LSF before submitting again.

3 Check the result and open your video

Replace PASTE_TASK_ID with that task ID, then run:

curl -sS \
  'https://ai-api.lightspeedfuture.com/v1/videos/PASTE_TASK_ID' \
  -H "Authorization: Bearer $LSF_KEY"

If the status is queued or in_progress, wait 30 seconds and repeat step 3 only. When it is completed, open the link in metadata.url and save your video.

Example response fields — your link will be different:

{"status":"completed",
 "metadata":{"url":"https://.../video.mp4"}}

Need help? Send your task ID and error message to [email protected]. Keep your API key private.

Next steps

Explore the Native video API · Download the one-page guide

Prefer automatic status checks? The optional starter uses Python 3.8+ and curl. The commands above work without it.

First Video Quickstart v1.1 · 17 November 2026

Quickstart · Markdown · Request JSON · Optional Python script

Choose either the curl commands or the optional starter for your first test. Running both creates separate tasks.

Advanced request IDs, safe retries and workflow responses

For the simplest first test, use the First Video Quickstart at https://lightspeedfuture.com/docs/quickstart/. It shows how to create a 5-second, 720p, 16:9 Native Seedance 2.5 video with curl and retrieve the video link. The direct curl example below uses the same settings; product-specific options follow in later chapters.

curl --request POST \
  'https://ai-api.lightspeedfuture.com/v1/videos' \
  --header 'Authorization: Bearer <LSF_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "model": "<YOUR_SEEDANCE_2_5_MODEL_ALIAS>",
    "prompt": "A ceramic cup on a desk in soft daylight.",
    "metadata": {
      "duration": 5,
      "resolution": "720p",
      "ratio": "16:9",
      "output_format": "mp4",
      "generate_audio": false,
      "client_request_id": "demo-native-001"
    }
  }'

Store the returned public task identifier with the exact submitted request and client_request_id. Retrieve that task using the same authorized key:

curl 'https://ai-api.lightspeedfuture.com/v1/videos/<YOUR_TASK_ID>' \
  --header 'Authorization: Bearer <LSF_API_KEY>'
Situation Action
Accepted / still processing Poll the same task every 30 seconds or longer. LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash advance automatically even when you do not poll.
Completed Read the documented result URL and copy the media to your own storage promptly.
Failed; or expired for Native video Read the error and review the balance adjustment. LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash currently expose completed and failed as their terminal states. A corrected, intentionally new job uses a new request ID.
GET timeout or connection loss Resume GET on the same task. Do not create another job.
POST outcome unknown Keep the original request ID and payload. If you have a task ID, use GET. Do not create a fresh request ID merely because the response was lost; contact LSF if the original task cannot be established.
Identical idempotent replay Reuse the original client_request_id only with the same logical request and unchanged payload. A changed URL or output setting is not an identical replay.

The initial charge estimate is not a guarantee of final duration or a spending cap. Keep sufficient available balance for the final charge adjustment after completion.

4.1 Request IDs and identical replay

Assign a unique metadata.client_request_id before the first POST. Save the exact request body, the key identity used for submission and the returned public task ID. Use a fresh ID for each intentionally new job.

Product Requirement Allowed ID
Native video Optional; recommended 1–128 characters
LSF Seedance 2.5 Production Optional; recommended 1–128 characters
LSF Seedance 2.5 Flash Required 1–128 characters
Seed Audio Optional; recommended 1–128 characters
LSF Video Enhancement Optional; recommended 1–64 characters

Use only letters A–Z and a–z, digits 0–9, and . _ : - . Submit IDs without leading or trailing whitespace. Video IDs share one namespace per API key across Native, LSF Seedance 2.5 Production, LSF Seedance 2.5 Flash and LSF Video Enhancement; do not reuse an ID for another product on the same key.

For LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash, a replay of an accepted identical request returns HTTP 200 with the task’s current state, rather than repeating the original HTTP 202 response. It does not create a new generation or reservation. Reusing an ID with a different request returns HTTP 409. Adding an explicit default, changing prompt whitespace or reordering reference items can change the request; replay the saved body unchanged.

Switching API keys creates a different idempotency scope and can create another billable task. Keep the original key, ID and body when a submission outcome is unknown. Once a task ID is available, resume GET instead of resubmitting to check progress.

Video deduplication depends on the accepted task record remaining available. This guide does not specify a fixed or permanent video-idempotency retention period. Native Draft eligibility, result-URL expiry and Seed Audio replay windows are separate rules.

Replay the saved request body unchanged. Do not rely on field normalization or infer one product’s replay rules from another. Seed Audio replay windows are described in section 9.8.

4.2 Production and Flash task responses

LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash use the response format in this section. Use the model alias supplied for the selected product. Native video, Seed Audio and LSF Video Enhancement have their own response fields, documented in their respective chapters.

Status Meaning Client action
queued Accepted and awaiting processing Save the task ID and poll.
in_progress The workflow is running Continue GET on the same task.
completed The final result is ready Read metadata.url and store the media.
failed The workflow ended in failure Read error and the reservation adjustment.

The first accepted POST returns HTTP 202. An accepted identical replay returns HTTP 200 with the current task state. GET returns HTTP 200 for a readable task, including a failed one; inspect status as well as the HTTP status. Progress values do not promise a completion time.

Accepted task

{
  "id": "task_example",
  "task_id": "task_example",
  "object": "video",
  "model": "<YOUR_PRODUCT_MODEL_ALIAS>",
  "status": "queued",
  "progress": 0,
  "created_at": 1792100000
}

Processing task

{
  "id": "task_example",
  "task_id": "task_example",
  "object": "video",
  "model": "<YOUR_PRODUCT_MODEL_ALIAS>",
  "status": "in_progress",
  "progress": 10,
  "created_at": 1792100000
}

Completed task

The following result is illustrative. The actual output length, frame rate and completion time depend on the request and delivered media.

{
  "id": "task_example",
  "task_id": "task_example",
  "object": "video",
  "model": "<YOUR_PRODUCT_MODEL_ALIAS>",
  "status": "completed",
  "progress": 100,
  "created_at": 1792100000,
  "completed_at": 1792100180,
  "seconds": "5.025",
  "metadata": {
    "url": "https://example.com/final.mp4",
    "duration": "5.025",
    "fps": "120",
    "resolution": "1080p"
  }
}

id and task_id identify the same public task. Read the final video from metadata.url. seconds, metadata.duration, metadata.fps and metadata.resolution are strings. created_at and completed_at use Unix seconds; completed_at is optional until recorded.

metadata.last_frame_url is present only when requested and successfully produced. Fields without a value are generally omitted. The response does not echo client_request_id: retain your own request-ID to task-ID mapping. Use the public task ID and the documented result fields for tracking and delivery.

Failed task

{
  "id": "task_example",
  "task_id": "task_example",
  "object": "video",
  "model": "<YOUR_PRODUCT_MODEL_ALIAS>",
  "status": "failed",
  "progress": 100,
  "created_at": 1792100000,
  "completed_at": 1792100180,
  "error": {
    "code": "PRODUCTION_PROCESSING_FAILED",
    "message": "PRODUCTION_PROCESSING_FAILED"
  }
}

Both products currently return PRODUCTION_PROCESSING_FAILED for a workflow failure. Submission errors are listed in section 11.1. A confirmed workflow failure releases the reservation; an unknown submission outcome or client timeout alone does not establish failure.

Download successful media promptly and retain it in your own storage. Result links have no uniform guaranteed retention period. Production video outputs support the authenticated original-file route in section 6.7; use the documented result URL for Flash. Do not infer download support across products.

Search documentation

Search pages and headings. Use Tab or arrow keys to move through results.

NEWSEEDANCE 2.5

Native Seedance 2.5 4K

Invite-only access on BytePlus
Available to you through LSF

Explore Native 4K