Creatomate · Rate Limits

Creatomate Rate Limits

Creatomate's primary throughput constraint is the rendering concurrency and monthly credit pool tied to each subscription plan rather than published per-second request limits. Renders are queued and processed asynchronously, so high request volumes are absorbed by the render queue; the binding limits are the included credits per month and the number of renders that can be processed in parallel. Specific per-plan concurrency and any HTTP request rate limits are not enumerated in this artifact.

Creatomate Rate Limits is the machine-readable rate-limit profile for Creatomate on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring renders, credits, and requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Media, Video Generation, Image Generation, Automation, and Templates.

3 Limits Throttle: 429
MediaVideo GenerationImage GenerationAutomationTemplatesRenderingRate LimitingQuotasThrottling

Limits

Render Concurrency project
renders
see provider documentation
Number of renders processed in parallel; varies by subscription plan.
Monthly Credits project
credits
see plan
Each plan includes a fixed monthly credit pool consumed per rendered output.
HTTP Request Rate project
requests
see provider documentation
Async queueing absorbs bursts; explicit per-second request limits are not published.

Policies

Asynchronous Queueing
Renders are queued and processed asynchronously; poll GET /renders/{id} or use a webhook rather than blocking on a request.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses.

Sources