Light Speed Future

DOCUMENTATION

Integration and Error Handling

On this page
Area Implementation guidance
Request construction Use exact model aliases and case-sensitive field names. Put documented controls under metadata. Keep ordered content roles intact.
Client records Store public task ID, client_request_id, selected alias, intended settings, creation time, terminal state and final response. Keep your own business lineage if needed.
Authorization Keep keys server-side. Follow the key-rotation rules in sections 2 and 5.8; a key in the same organization does not automatically have access to every task.
Retry Use the same task ID for GET recovery. An ambiguous submit response is not permission to create a fresh job. See section 4.
Media access Use stable, direct media URLs. Allow enough access time for validation, queueing and processing. Copy temporary results promptly.
Billing Use the selected product’s rules: Native by actual usage; Native Draft and Final as separate tasks; LSF Video Enhancement quoted per minute and charged by output seconds/FPS band; LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash by finished-video chargeable seconds without an FPS surcharge; Seed Audio by original_duration. Use the effective account rate once.
Playback High-resolution or high-bit-depth output may need compatible codecs and players. Verify client playback requirements before selecting advanced controls.
Error parsing Handle the standard error envelope and task status. Do not depend on exact message wording or undocumented service details.
{
  "error": {
    "message": "metadata.video_url must be a public HTTP or HTTPS URL.",
    "type": "invalid_request_error",
    "param": "metadata.video_url",
    "code": "invalid_request_error"
  }
}

An HTTP success response from an asynchronous create endpoint indicates acceptance, not successful video delivery. Always use the terminal task result for delivery and final billing.

Maintenance, conflicts and task access

Response / situation Client action
HTTP 503 during scheduled maintenance New video submissions may receive an English JSON maintenance message with Retry-After and Cache-Control: no-store. Respect Retry-After. Keep the original request and client_request_id if the POST outcome is uncertain.
Existing tasks during maintenance Continue GET through the documented HTTPS endpoint. A service switch can briefly interrupt access; resume GET on the same task afterward.
HTTP 409: request ID reused with different parameters Follow section 4.1 for each product’s request-ID rules. LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash return PRODUCTION_REQUEST_CONFLICT for a different request under an accepted same-key ID. New Native records can return idempotency_conflict. Preserve the original payload during recovery.
Task access denied after account/access changes Retain the original task ID and contact LSF. Do not assume that a replacement key or changed access context can read every historical task.

Parse the HTTP status, structured error when present and Retry-After. Do not match one exact English error sentence: message wording may change while the documented error handling stays the same.

11.1 Production and Flash task errors

LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash share the following error codes. The list does not replace authentication, rate-limit or edge-proxy errors. For asynchronous failures, inspect the task status returned by GET as described in section 4.2.

HTTP Code What to check
400 invalid_client_request_id Required LSF Seedance 2.5 Flash ID is missing or invalid.
400 PRODUCTION_REQUEST_FIELD_INVALID / PRODUCTION_METADATA_REQUIRED Top-level fields or metadata structure.
403 PRODUCTION_MODEL_NOT_AUTHORIZED / VIDEO_TENANT_NOT_AUTHORIZED / PRODUCTION_CONFIGURATION_NOT_READY Assigned alias, key permissions and product availability.
409 PRODUCTION_REQUEST_CONFLICT Same-key ID was used for a different request.
409 PRODUCTION_RESERVATION_NOT_ACCEPTED Reservation or acceptance did not complete. This code alone does not identify the cause.
422 PRODUCTION_REQUEST_INVALID Parameter combination or enabled output configuration.
422 PRODUCTION_TIN_UNAVAILABLE Reference video could not be measured reliably.
404 PRODUCTION_TASK_NOT_FOUND Task ID, original account ownership and current key permissions.
503 PRODUCTION_ADMISSION_DISABLED / PRODUCTION_RECOVERY_UNAVAILABLE / PRODUCTION_STATE_UNAVAILABLE Temporary submission, recovery or state availability. Preserve the original request.

For example, missing client_request_id on LSF Seedance 2.5 Flash returns HTTP 400 before a new task is accepted:

{
  "error": {
    "type": "production_error",
    "code": "invalid_client_request_id",
    "message": "invalid_client_request_id"
  }
}

A rejected request may have no task ID. Retain its HTTP status, structured error, timestamp, original request ID and any request identifier in the response. Contact LSF with these details and a redacted request if necessary. Do not change IDs or keys automatically after a timeout or temporary error, because the original submission may already have been accepted.

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