How to Access Seedance 2.0: From Nothing to First Clip
How to access Seedance 2.0 step by step: choosing a surface, getting a key, the fields a first request needs, what it costs, and why a first call fails.
There is no consumer app published by ByteDance that hands you Seedance 2.0 directly. How to access Seedance 2.0 in practice means picking one of the surfaces that resell the model, getting a credential, and sending a correctly shaped request. This page walks that path end to end, with the cost of the first clip and the four reasons a first call usually fails.
None of it takes long. Most of the difficulty sits in what each surface quietly decides on your behalf.
The surfaces that carry the model
Access arrives in three shapes, and which one you pick determines what you can control.
A consumer video app gives you a text box, a few presets and a credit balance. No key, no code. It is the fastest route to a first clip and the one that hides the most: duration caps, resolution downgrades and watermarks are applied by the app rather than the model, and you often cannot tell which version you are being served.
A hosted API gives you a key and the raw request. Every parameter the model exposes is reachable, billing is per second of finished video rather than per credit, and you can read the actual error when something fails. It requires you to send HTTP.
A bundled integration puts the model inside an editing or design tool you already pay for. Convenient if you live in that tool, and the parameter set is usually the narrowest of the three.
For anything beyond a first look, the API route is the one that tells you the truth about what you are getting.
What you need before the first request
Three things.
An account on whichever platform you chose, with billing attached. An API key, issued from the platform dashboard and sent as an Authorization: Bearer header. And, if you plan to condition the generation on an image, a publicly reachable URL for that image. Media inputs must be public HTTP or HTTPS links. Data URIs are rejected across the platform, so a file on your laptop has to be uploaded somewhere first.
Keys are bearer credentials. Anyone holding one can spend your balance, so keep them server side and out of the browser bundle.
How to access Seedance 2.0 through the hosted API
The call is a POST to the platform's video generation endpoint with a JSON body, and it returns a task id rather than a video. Four fields carry the whole request:
- the model identifier, copied exactly from the official documentation for the version you want
- the prompt, a shot description rather than a mood board in words
- the duration in seconds, which on 2.0 cannot exceed 15
- the resolution, one of 480p, 720p or 1080p
There is no 4K setting. That ceiling is the same on every host, and a page advertising 4K for this model is repeating a pre-release claim.
Copy the model string rather than typing it from memory. Identifiers in this family are versioned precisely, and older code samples circulating online quote strings that no longer resolve. A wrong identifier fails validation before a task is created, so it costs nothing, but it produces an error that reads like an access problem rather than a typo.
Polling, and the wait
Generation is asynchronous. The create call returns immediately with a task id, and you poll a task endpoint until the status turns terminal. Polling is free, which means there is no reason to back off aggressively.
Expect two to five minutes. A job still incomplete at twenty minutes has gone wrong, and the refund path is the same as for any other failure.
When the task succeeds, the response carries a URL for the finished file. Download it. Hosted result URLs are not a permanent archive.
What the first clip costs
Billing is per second of finished video, priced by resolution. The published rates for Seedance 2.5 are below and act as an upper bound for 2.0, which is priced lower per second:
| Resolution | 2.5 generation only | 2.5 with a reference video |
|---|---|---|
| 480p | $0.118589 | $0.071153 |
| 720p | $0.266824 | $0.160094 |
| 1080p | $0.461856 | $0.275904 |
A five-second 480p clip on 2.5 is roughly $0.59, and on 2.0 it is less. That is what a first render should cost you. Start there rather than at 1080p, confirm the pipeline works end to end, then raise the resolution once you know the prompt lands.
Failed jobs are refunded in full, including refusals from content moderation, so an experiment that goes wrong is not a charge.
Why a first call fails
Four causes account for most of them.
Duration above 15 seconds. A hard ceiling on 2.0, rejected at validation. If you need longer, the target is Seedance 2.5, which runs to 30.
A local or data: media URL. Rejected platform-wide. Upload and pass a public link.
A retired model string. Validation error, no task created, no charge.
A safety refusal, returned as error 80006. It does not name the stage that fired, so the prompt, a reference image and the generated output are all candidates. The content_filter parameter defaults to true and setting it to false routes to a less restrictive channel without disabling moderation. Beneath that, the model blocks named real celebrities, third-party intellectual property and illegal content, and no host setting changes that.
Frequently asked questions
Can I access Seedance 2.0 without writing code? Yes, through a consumer app or a bundled integration in an editing tool. You trade parameter control and per-second pricing for a credit balance and someone else's presets.
Do I need a separate key for 2.0 and 2.5? No. Platforms that serve both expose them as different model identifiers under the same account and the same key. Switching versions is usually a one-string change.
How long until the first video exists? Two to five minutes after the request is accepted. The create call itself returns in under a second with a task id, which is what confuses people expecting a video in the response.
Is a failed generation charged? No. Failures are refunded in full, refusals included. Check the credits figure on the finished task to confirm the reserve came back.
The short version
How to access Seedance 2.0 is three decisions and one request. Choose a surface, knowing that a consumer app hides the version and the caps while an API key exposes both. Get the key, keep it server side, and host any reference image at a public URL. Send a POST with the model string, a prompt, a duration at or under 15 seconds and a resolution, then poll for two to five minutes. Make the first one 480p and five seconds. It costs cents, and if it fails you are refunded.
