On this page
Short answer
On the KreatorFlow API you can create 20 per minute Seedance video jobs and poll 120 per minute per developer account. Over the limit you get a 429 with a Retry-After header. Jobs run in the background, so a batch is many quick creates plus webhooks, not many open connections.
Get started
Batch Seedance clips without hitting limits
- 1
Create, do not wait
POST /v1/videos returns at once with a job id; the clip renders in the background.
- 2
Pace creates
Stay under 20 per minute; for big batches, send them from a queue at a steady rate.
- 3
Use webhooks
Pass webhook_url instead of polling every job, so polling never eats your limit.
- 4
Back off on 429
Wait the seconds in Retry-After, then resend with the same Idempotency-Key.
Rate limits per developer account
| Endpoint | Limit |
|---|---|
| POST /v1/uploads | 60 per minute |
| PUT /v1/uploads | 60 per minute |
| DELETE /v1/uploads/{upload_id} | 60 per minute |
| GET /v1/storage | 60 per minute |
| POST /v1/images | 60 per minute |
| POST /v1/characters | 60 per minute |
| GET /v1/characters | 60 per minute |
| GET/DELETE /v1/characters/{character_id} | 60 per minute |
| POST /v1/videos | 20 per minute |
| POST /v1/video-edits | 20 per minute |
| GET /v1/jobs/{job_id} | 120 per minute |
| GET/HEAD /v1/jobs/{job_id}/output | 300 per minute |
| API key creation | 5 per 600 s |
How often should I poll a Seedance job?
Every 10 to 15 seconds for video is plenty; a clip takes minutes, not seconds. Better still, use a webhook and keep a slow sweep for anything that never reported back.
Can I get higher limits?
If your product needs more, contact support with your expected volume.
Frequently asked questions
What is the Seedance API rate limit on KreatorFlow?
20 per minute for POST /v1/videos and 120 per minute for GET /v1/jobs/{id}, per developer account.
What happens over the limit?
The request returns 429 with a Retry-After header. Nothing is reserved.
Are limits per key or per account?
Per developer account, shared by all its keys.
