Public API
Pending
Not represented as generally callable.
Developer watch
Seedance 2.5 API
A verification-first guide to availability, model IDs, pricing, request fields, and production readiness. No placeholder endpoint is presented as a working API.
Model ID
Not published
No guessed identifier.
Pricing
Pending
Waiting for the Ark model card.
Request schema
Not verified
Fields will follow first-party docs.
Current answer
What is actually known
The expected consumer release and Ark catalog update do not, by themselves, prove public API access. This page treats the model card, playground, and callable endpoint as separate milestones.
Until a first-party API reference is published and a general account can complete the workflow, the honest integration status is pending. That means no endpoint, model ID, duration limit, resolution tier, or billing rule should be hardcoded as a Seedance 2.5 fact.
Catalog visibility
A model can appear with descriptive information and pricing before execution is enabled.
Account eligibility
Enterprise allowlists, regions, verification, or quotas may affect who can call a model.
Playground access
A console demo may use permissions or defaults that differ from API access.
Production access
A usable API needs stable authentication, jobs, errors, limits, and billing.
Architecture
Prepare without guessing
You can design the application boundary now while leaving provider-specific values unset. Video generation should be modeled as a job rather than a synchronous text response.
- Keep provider, region, endpoint, and model ID in server-side configuration.
- Separate asset upload and validation from generation submission.
- Store a provider task ID and map provider states to your own job states.
- Support polling and webhooks without assuming either will launch first.
- Set per-user cost ceilings, concurrency limits, retries, and timeouts.
- Do not send keys, copyrighted references, or portrait assets from browser code.
Launch checklist
Verify before the first call
When documentation appears, confirm authentication, regional host, model identifier, request fields, accepted asset URLs, duration and resolution limits, output retention, moderation errors, cancellation, and billing.
A single successful playground result is not enough for production. Run a small test matrix covering text-only, image reference, rejected content, invalid assets, timeout behavior, duplicate submissions, and cost reporting.
API FAQ
Developer questions
Is the Seedance 2.5 API public?
It is marked pending on this tracker. No general-access model ID, endpoint, request schema, or verified account workflow is published here yet.
Why not publish an example request now?
A placeholder model name can look runnable even when it is not. This page will add code only after first-party documentation provides a real identifier, authentication method, fields, and response lifecycle.
Can I prepare my application before launch?
Yes. Keep the provider and model ID configurable, design video work as asynchronous jobs, validate uploaded assets separately, and add cost and retry limits before enabling production traffic.
Will Ark console access guarantee API access?
Not necessarily. A catalog card, price listing, playground permission, and callable API can become available at different times and for different account types.
API alert
Get notified when a real endpoint is documented.
The alert changes only when model access, documentation, pricing, or a callable API can be verified.