Bannerbear · Rate Limits

Bannerbear Rate Limits

Bannerbear enforces a documented API rate limit of 30 requests per 10 seconds per API key. Separately, each subscription plan caps the number of image/video API credits that can be consumed per month; unlike per-request throttling, the monthly credit cap is a hard quota that cannot be exceeded without upgrading the plan. Async create requests return 202 and do not block on render time, so request-rate limits apply to the submission and polling calls rather than to render duration.

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

It captures 5 rate-limit definitions, measuring requests, credits, and seconds.

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

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

5 Limits Throttle: 429
Image GenerationVideo GenerationTemplatesMediaAutomationRate LimitingQuotasThrottling

Limits

Requests Per 10 Seconds api_key
requests
30 per 10 seconds
Documented global API rate limit across all endpoints for a given API key.
Monthly API Credits (Automate) account
credits
1000 per month
Hard monthly cap on the Automate plan; cannot be exceeded without upgrading.
Monthly API Credits (Scale) account
credits
10000 per month
Hard monthly cap on the Scale plan.
Monthly API Credits (Enterprise) account
credits
20000+ per month
Starts at 20,000 and scales up to ~2,000,000 via Enterprise arrangements.
Synchronous Timeout request
seconds
10 second timeout
Synchronous host (sync.api.bannerbear.com) returns 408 if a render exceeds 10 seconds; use async + webhook/poll instead.

Policies

Hard Monthly Quota
Image/video credit limits cannot be overrun; the account must upgrade to a higher plan to continue generating.
Backoff Strategy
Clients should throttle to stay within 30 requests / 10 seconds and implement exponential backoff with jitter on 429 responses.
Async Submission
Prefer asynchronous create + webhook or polling over the synchronous host to avoid 10-second timeouts on heavier renders.

Sources