Skip to main content
Request limits depend on the deployed API gateway and service configuration. The current Podcast contract does not publish a universal requests-per-second or generation-concurrency quota. Use bounded concurrency, honor HTTP 429 and Retry-After when present, and retry transient read failures with exponential backoff and jitter. Ask support about capacity for your workload.

​
Poll asynchronous tasks

A practical client starting point is one poll every 3-5 seconds, increasing the interval for long renders. This is a client recommendation, not a service limit or completion-time guarantee. Stop when the operation reaches a terminal state and enforce a timeout in your application. Queueing and provider generation time are separate from HTTP request duration. Keep the returned native task and project IDs so another process can resume monitoring.

​
Retry generation deliberately

Do not resubmit generation on each poll or automatically submit a new job after a network timeout. Use idempotency and status checks to resolve whether the original request was accepted.