Seedance API guide: choose a route, submit a task and inspect the video

A Seedance API integration needs more than a generation request: it needs the correct provider route, valid reference inputs and a completed-task check. This guide covers Seedance 2.0 and 2.5 through Nexscope. It is not ByteDance’s official API documentation, and Nexscope authentication and billing should not be copied into another provider’s integration.

Open Seedance 2.0 Playground · Open Seedance 2.5 Playground. New users receive 1,000 free credits, valid for 3 days. API key access requires an active subscription; the trial does not guarantee a free generation on every route or configuration.

Quick answer: Select the exact version, check access and cost, and provide a compatible reference. Submit the request, retain its task ID, then inspect the completed result rather than treating a submission receipt as a video. For product footage, manually review identity and motion before approving the asset.

Documentation checked October 23, 2026. Written by Nexscope Team. This is an integration guide, not a new generation benchmark. No chargeable API request was run for this article.

Seedance 2.0 API vs 2.5 API: which route do you need?

Choose by the input and output requirements of the shot. A newer version’s larger allowance does not establish better motion, fewer retries or a lower cost for your task.

Check the live Seedance 2.0 contract or Seedance 2.5 contract before sending production requests. In particular, reference-video mode cannot be combined with image-reference inputs. Do not add every available reference field to the same payload.

For editorial strengths, limitations and attributed public feedback, read the 2.0 review and 2.5 review. The guide here focuses on the integration decision rather than repeating those reviews.

Can you use a free Seedance API key?

Nexscope’s creative API key access requires an active subscription. The advertised new-user trial is a finite app trial balance, not permission to call every creative API. Do not build an integration on the assumption that receiving credits automatically enables a key.

Check current plans and access conditions, then manage the key in your own account. Keep it server-side; never embed it in public browser code, a repository, a screenshot or a support post. Use a placeholder when sharing a reproducible request.

How do you start a Seedance API request?

Start from the live route example, not a guessed endpoint or an example for another provider. Nexscope documents Bearer authentication and route-specific JSON inputs. The 2.0 submission endpoint is https://api.nexscope.ai/video/seedance20VideoGeneration; 2.5 uses a separate endpoint in its linked documentation.

Prepare the following before calling:

1. A valid API key with the required subscription access and enough usable credits.
2. A product image or other supported reference that you are permitted to use.
3. A concise description of one shot, including the motion and product details that must remain unchanged.
4. A supported duration and resolution, plus other fields required by the current contract.
5. A record of the request estimate, model version and settings for later reconciliation.

The documentation examples contain illustrative URLs. Replace them with a retrievable asset; a placeholder URL is not an uploaded reference. Consider the privacy implications of exposing a reference URL and do not publish private or unauthorised source material merely to make an example run.

What happens after submission?

A task ID is a receipt, not a downloadable video. Preserve it with the route and request settings. Follow that route’s current task-result instructions until it reaches a terminal outcome; do not assume a fixed completion time.

Your integration should distinguish these stages:

Do not submit another generation just because the first is slow. That can create another chargeable task. If a submission response is ambiguous, investigate its task or usage record before retrying. Parse the response described by the current route; do not assume every endpoint uses an identical wrapper.

How much does the Seedance API cost?

Use the request-specific estimate and completed charge, not a fixed price copied from an old comparison. Duration, configuration and provider billing all matter. At this review date, Nexscope’s plan examples and some route-level estimates are not directly reconciled, so this guide does not promise a fixed credit-per-second rate.

If no estimate is available, clarify the cost before sending a paid request. During a pilot, save all charges, including rejected outputs, and calculate credits per approved clip. A successful task status does not establish creative acceptance or product fidelity.

What should a product-video pilot test?

Use a single clear product reference and a simple camera movement. Keep the intended object and scene easy to judge. A modest brief makes it easier to distinguish an input problem from a product-preservation failure.

For a hypothetical bottle, a brief could request a slow camera move around the stationary item while preserving its cap, silhouette, printed label and color. This is suggested input, not an output we generated. Review the whole video for changing geometry or packaging, invented accessories and unsupported implied functions.

Log the input asset, prompt, route, settings, task ID, completion status, output, actual charge and rejection reason. Before automation at scale, decide what your application does with failed tasks, unusable completed media and uncertain product details. Do not auto-publish a video based only on completion status.

Playground or API: where should you begin?

Use Playground to inspect the available settings and access conditions before implementing a client. Use the API when you need repeatable server-side automation and have confirmed its billing and task lifecycle. The simplified app and external API may expose different controls.

For a complete content workflow, continue to the AI product video guide. For other model choices, browse the model review directory.

Last reviewed: 2026-10-23 · Maintained by the official Nexscope team · Editorial & evidence policy.