Doubao2API · Control room

Queue policy

Bundles collect for a fixed window. Carpools collect until full; each job starts independently.

Account readiness

Quota units are not video counts. Account traffic uses its assigned proxy; storage transfers are direct.

Recent jobs · last 24h

New generation

Seedance 2.5

HOW IT WORKS

A place for every request.

Upload & validateYour media is stored privately and checked before admission.
Prepare the canvasAn available account is assigned. Audio conversion and uploads begin.
Start generationThe system chooses a bundle or carpool. Bundles wait for all viable jobs to be ready; carpool jobs start independently.
Receive your resultEach job finishes independently. Download its verified video from Jobs.

Submitting uses account quota. Requests with uncertain upstream acceptance are held for review, never blindly resubmitted.

Generation history

ROLLING LAST 24 HOURS · LIVE WORKLOAD

Queue performance

Live

— completed jobs · — processing · incoming last 4m: — · last 10m: —

Bundles share one account and canvas, then submit when all viable jobs are ready. Carpools give each job its own account and canvas, starting independently while collection continues.

Refreshes every 10 seconds

Batch details

All jobs in this collection

Expand a job to see its full prompt, parameters, ordered media references and result details.

Account checks run on import, before batch use, and at 00:01 / 12:01 GMT+8. 今日免费已生成 resets at 00:00 GMT+8.

Mailbox

Account checks, proxy recovery and admin actions.

Moma comparison baseline

Captured requests and provider outcomes, with results from the explicit ten-job replay.

Full prompts, parameters and media are held in the protected comparison dataset on heavyworker. Reference markers are translated to Doubao syntax for replay; original media and prompts are preserved.

GENERATION WORKSPACE

Settings

Shape how jobs arrive, share accounts and move through generation.

Live controls

New requests

Pause intake without interrupting accepted work.

Accept new requests

01

Collection strategy

The system assigns every job. If one mode is unavailable, it tries the other.

When neither mode has an eligible account or capacity, new work is not collected. Account reservations prevent overlapping assignments.

02

Distributed worker strategy

Keep each whole bundle or carpool on one worker. Every job in that batch follows the same owner.

Blank batch limit means no limit. Collecting and processing batches count toward the cap. Lowering a cap drains existing work. An offline worker's unfinished jobs fail and are never reassigned; a verified recovery accepts new batches only.

Bundle

Enabled

One account, one canvas, multiple jobs. Collect first; submit when all viable jobs are ready.

Checking capacity…

First downloadable result ends retries

Retries stop when the provider confirms a video is ready. Remaining confirmed failures revive or fail; accepted generations continue to be monitored.

Account tags

7-day only and available → 5-hour and 7-day available

Carpool

Enabled

One account and canvas per job. Each job prepares and starts independently.

Checking capacity…

Collection closes only when full

No collection timer. The lifetime limit applies to each job’s work; retries keep the same account and canvas.

Account tags · in priority order

7-day only used up → 5-hour available / 7-day used up → both used up → unique counter 7 days used up. 今日免费已生成 must be false.

03

Capacity & safeguards

Shared limits apply across bundles and carpools.

The original job clock includes collection and every revival. Ambiguous submissions are reconciled; they are never automatically replayed.

04

Worker capacity

Apply live. Lower counts let active calls finish before taking effect.

05

Media & storage

Storage capacity and automatic retention.

Unused inputs: 1 hour. Referenced inputs: all jobs terminal + 1 hour. Results: 24 hours. Active and uncertain work stays protected.

06

Account checks

Verified before use, with a pinned proxy.

GMT+800:01 & 12:01

Also runs on import and before a batch uses an account.

Checks enable material compliance and image/video watermark removal when needed. The shared daily-use flag resets at midnight. There is no 24-hour success cooldown.

Manage accounts →

Advanced transfer controlsTimeouts, per-canvas upload limits and polling

Settings are up to dateNew collection policies apply to new groups. Accepted work keeps its frozen policy.

One key. Dashboard and API.

Send Authorization: Bearer YOUR_API_KEY or X-API-Key. Never put your key in a URL.

Method	Endpoint	Purpose
POST	api/media	Upload one multipart file; returns media ID
POST	api/jobs	Create a durable job; requires Idempotency-Key
GET	api/jobs/{id}	Read job status
GET	api/jobs/{id}/result	Download a completed MP4
GET	api/accounts	Read account quota and status
GET	api/queues	Read batches and timers
GET	api/openapi.json	Authenticated API schema

States: preparing → ready → submitting → running → downloading → succeeded. Failures are separate; needs_attention preserves uncertain jobs for reconciliation.

Capacity exhaustion returns 429 with Retry-After. No eligible account returns 503. Reuse the same idempotency key and request body after an uncertain client response.