Bannerbear
DESIGN · FILES & DOCS
Templates, image and video renders, and batches run on their own key.
Connect Bannerbear with Fabriq Developer
Your user pastes their Bannerbear credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Bannerbear in practice
Bannerbear is asynchronous by default: a POST returns 202 Accepted and the finished image arrives by webhook or polling, so an agent that reads the POST response body gets no image. Bannerbear also publishes two different rate limits for itself — 60 POST requests per 10-second window in the API reference, 30 requests per 10 seconds in the help centre — and neither page says which API version its figure describes.
Scopes that draw scrutiny
Master API Key (Full Access)Bannerbear’s wording is that it "grants complete access to all projects and API endpoints". It also changes the request shape: with one "you need to add a project_id parameter to your requests", which a project key must not send.An unscoped V5 keyThe permissive default rather than the restrictive one: "An unscoped key has full access." Omitting the scope list is what grants everything.images:write, animations:write, workflows:writeThe V5 write scopes. Every call they permit consumes monthly API credits, so these are the scopes that cost money per request rather than merely reading data.webhooks:read-writeLets a key change where generated media is delivered, which redirects output rather than reading it.
Rate limits
- The API reference states "The Bannerbear API rate limit is 60 POST requests per 10 second window." The help centre states the limit "is currently 30 requests per 10 seconds". Exceeding it returns 429.
- Monthly API credits are a separate budget that resets on the 1st of each month for paid plans: 1,000 credits on Automate at $49/month, from 10,000 on Scale at $149/month, from 50,000 on Enterprise at $299/month. "Trial accounts get a fixed non-renewable 30 API credits."
- Exhausting the credit quota returns 402 Payment Required — "Your API quota is exhausted. Upgrade to continue" — not 429.
- Synchronous requests to sync.api.bannerbear.com carry "a timeout of 10 seconds" and return 408 past it.
Worth knowing
- The synchronous escape hatch is a different host, sync.api.bannerbear.com, and its ten-second timeout means anything slower has to go back to webhooks or polling.
- Two live API generations need their own credentials: "V5 API Keys are not compatible with V2 endpoints, and vice versa."
- Credits do not carry over and cannot be topped up, so quota exhaustion is a runtime 402 that only a plan upgrade clears — it is not a billing detail you can settle later.
- Swapping key type changes the request body as well as the permission, because a Full Access master key requires a project_id parameter on standard endpoints that a project-scoped key omits.
Checked against Bannerbear API reference (2026-09-29), Bannerbear V5 API (2026-09-29), What are the Bannerbear API keys (2026-09-29), Why am I seeing a 429 (2026-09-29), Bannerbear pricing (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Bannerbear behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.