Most older Seedance API tutorials are now misleading.
The outdated version usually claimed all of the following:
- a public base URL like
api.seedance.ai - a Dreamina-style developer portal
- self-serve API keys for any user
- fixed per-generation pricing
As of April 3, 2026, that is no longer the safest way to explain Seedance API access.
Related: Read the updated pricing guide, check the current free access guide, open the main Seedance 2.0 page, or use the new availability guide to separate consumer rollout from API access.
What Changed on April 2, 2026
On April 2, 2026, Chinese media reported that Volcengine opened Seedance 2.0 API public beta for enterprise users. Volcengine's official Seedance API documentation also shows an updated timestamp of 2026-04-02 17:25:16.
That means the current API story is:
- China enterprise first
- Volcengine / ModelArk first
- public beta, not a globally uniform self-serve rollout
The Verified Access Model
If you want the safest current description of Seedance API access, use this:
1. China API access runs through Volcengine / ModelArk
The official documentation to reference is Volcengine's Seedance 2.0 API page, not an unofficial api.seedance.ai guide.
2. Enterprise activation matters
The April 2 public beta reports describe enterprise-user access. In practice, that means you should expect:
- account verification
- model activation
- console-side permission management
- contract and billing review for production usage
3. Billing is now better described as token-based pay-as-you-go
For current pricing language, see the updated Seedance pricing guide. The important point for developers is that older flat per-generation API pricing claims are no longer reliable enough to repeat as official truth.
What Older Seedance API Guides Get Wrong
Wrong: "The official base URL is api.seedance.ai"
We are removing that claim because the current verified China API story points to Volcengine / ModelArk documentation and onboarding instead.
Wrong: "Any user can create a Seedance API key in Dreamina"
That no longer matches the April 2 China public beta story. The safer explanation is enterprise-oriented access and activation through Volcengine.
Wrong: "The Seedance API is globally open"
That is too broad.
BytePlus's official Digital character library page explicitly said Seedance 2.0 was available only through Model Playground within the free quota there, and that API invocation was not supported at that time. So consumer availability and global developer API availability are still uneven.
Consumer Rollout Is Not the Same as API Access
This distinction matters more now than before.
Consumer rollout
CapCut's official newsroom said on April 1, 2026 that Dreamina Seedance 2.0 was rolling out gradually to paid CapCut users. The first listed markets were Indonesia, the Philippines, Thailand, Vietnam, Malaysia, Brazil, and Mexico, with more expansion planned.
That confirms consumer-product rollout in some overseas markets. It does not mean the developer API is uniformly open outside China.
Developer API access
The verified API story is narrower:
- China enterprise public beta on Volcengine
- global availability still staged
- regional documentation matters
So do not write "Seedance is available in CapCut" and then assume "therefore the developer API is open everywhere." Those are different claims.
Real-Person Faces, Avatars, and Compliance
Another place older Seedance API guides go wrong is by assuming full real-person and avatar workflows are open by default.
What we can verify publicly:
- BytePlus said real human images are not supported in that standard Seedance 2.0 flow
- the same page points users toward platform-provided virtual characters
- CapCut's official newsroom said safeguards were added to prevent unauthorized use of people's likeness and intellectual property
- the initial rollout also restricted some accounts from generating from images or videos that contain real human faces
So if your product depends on:
- face-based identity locking
- custom avatar libraries
- real-person likeness workflows
you should treat them as a separate compliance and product-availability track, not a default capability you can promise from the public API story alone.
For a more focused breakdown, read the Seedance real-human-face rules guide.
Reported Sales-Side Limits You Should Confirm Directly
April 2 Chinese media and creator discussions also mentioned:
- default 10-concurrency limits for new users
- high security deposits
- stronger restrictions for real-person faces and custom virtual characters
We have not found a public official contract page that cleanly verifies all of those terms line by line, so we are not writing them as universal official documentation.
The safe developer stance is:
- treat them as reported commercial terms
- confirm them directly with Volcengine before making roadmap promises
How to Approach Integration Now
If you are in China and need enterprise API access
Use this sequence:
- Complete the required Volcengine account and enterprise setup.
- Activate or apply for Seedance 2.0 access in ModelArk.
- Read the official Volcengine API reference before coding.
- Validate billing, rate limits, moderation constraints, and task concurrency with small-volume tests.
If you are outside China
Use this sequence:
- Check current BytePlus regional documentation first.
- Separate consumer rollout news from developer API availability.
- Do not assume an older unofficial SDK or blog post still reflects the production path.
- If your product depends on real-person faces or avatars, confirm those regional restrictions separately.
FAQ
How do I get a Seedance API key now?
The safest current answer is through the Volcengine / ModelArk enterprise-oriented flow in China, not through older Dreamina-style self-serve guides.
Is Seedance API globally available?
Not in a way we would describe as fully uniform. Consumer rollout and global API availability are still different stories.
What is the current Seedance API pricing model?
Use the April 2026 China-side token-billing framing rather than older flat per-generation claims.
Does Seedance API support business usage?
Yes, the current China public beta story is explicitly enterprise-oriented, but exact rights and limits depend on your contract and product path.
Why do older guides still use api.seedance.ai?
Because many of them were built on older unofficial assumptions or outdated onboarding paths. The safer references now are Volcengine / ModelArk and current BytePlus documentation.
Should I trust old cURL examples and unofficial SDK wrappers?
No. Check the latest official Volcengine reference first, because April 2 materially changed the reliable access story.
Sources and Verification Notes
- Volcengine Seedance 2.0 API reference
- BytePlus official: Digital character library
- CapCut newsroom: Dreamina Seedance 2.0 launch
- IT之家: Seedance 2.0 API opened public beta on April 2, 2026
Next Steps
- Check pricing: read Seedance pricing
- Check free access separately: read Seedance free guide
- Check route-by-route availability: read Seedance availability guide
- Open the main model page: visit Seedance 2.0
