Sync Labs batch API (20 to 500) vs Sume bulk runs (1 to 100)
Sync Labs batch takes 20 to 500 lip sync generations in one JSONL file on Scale and Enterprise. Sume bulk runs queue 1 to 100 Format runs with a 1 to 16 window.
Sync Labs' Batch API takes 20 to 500 lip sync generations in one JSONL file, targets a 24-hour turnaround, and is limited to Scale and Enterprise plans. Sume has no batch file: bulk runs queue 1 to 100 Format runs in one request, with a concurrency window of 1 to 16 that you poll while it runs.
Sync facts are from its batch guide; Sume facts from Bulk runs, read 2026-10-01.
What are the limits on each side?
| Topic | Sync Labs Batch API | Sume bulk runs |
|---|---|---|
| Size per request | 20 to 500 generations | items: 1 to 100 entries |
| Format | JSON Lines file, up to 5MB | JSON body, each item the same body as one run |
| Parallelism | Bypasses normal concurrency; separate cap on active batches | concurrency: required integer 1 to 16 |
| Turnaround | Target 24 hours | Poll queue status; no stated target |
| Availability | Scale and Enterprise only | No plan gate stated on the bulk-runs page |
What is the unit of work on Sume?
A bulk request is a server-side queue of ordinary Format runs, not a lip sync batch. Each item is one sandbox, one agent turn and one run receipt. Sync's batch guide also says only inputs up to 30 seconds are supported in batch processing.
How do I submit a batch on Sume?
Send concurrency and items with a fresh Idempotency-Key for every batch: replaying a spent key returns 202 with the old queue. One bad item fails the whole create with 400 invalid_request before anything is dispatched. Poll the queue's status_url; completed means every item is terminal, so branch on counts.failed. Similar limits are compared in Gemini batch vs Sume bulk runs.
Is the concurrency window a rate limit?
No. The admission docs call concurrency a dispatch limit, not a submit limit, so queued work waits for a slot instead of being rejected, as long as queue capacity remains.
Sources
Related posts
More in Developers
- Sync Labs API rate limit: 100 per minute, and Sume headers
Sync Labs allows 100 POST /v2/generate and 600 GETs a minute. Sume has a per-plan requests-per-minute budget; read ratelimit headers and retry-after.
- Sync lip sync output: H.264 crf 17, HDR to SDR, alpha removed
Sync re-encodes lip sync output to H.264 at crf 17, turns HDR into SDR and drops alpha. Here is that next to what Sume returns for avatar video.
- Sync sync_mode bounce, cut_off, silence, remap vs Sume lengths
Sync offers bounce, cut_off, silence and remap when audio and video lengths differ. Sume has no such option: trim or split audio to the accepted window.
- Synthesia Billing API credit usage vs Sume's /v1/usage ledger
Synthesia added a Billing API endpoint for credit usage. Sume's equivalent is GET /v1/usage: reservations, captures and refunds, filterable by run or job.
Written by Sume