Rate limits and concurrency
Understand per-minute request limits, concurrent task limits, and how to back off.
Two independent limits
Accounts have separate per-minute request buckets and a concurrent generation limit.
| Limit | What it caps | Default | Header on rejection |
|---|---|---|---|
| Submission | createTask, queued cancellation, upload tickets, and explicit asset completion | 100 / minute | Retry-After |
| Task polling | recordInfo | 120 / minute or 20 × the concurrency limit, whichever is higher | Retry-After |
| Account reads | Media quotes, submission receipts, temporary upload confirmation, and account balance | 120 / minute | Retry-After |
| Concurrent tasks | How many generation tasks run at the same time | 10 | Retry-After |
Exceeding either returns HTTP 429. The request is not charged and no task is created.
Response headers
When you are rate limited, the response includes Retry-After in seconds. Wait at least that long before the next attempt.

