Quota

Documentation Index

Fetch the complete documentation index at: https://documentation.bannerify.co/llms.txt

Use this file to discover all available pages before exploring further.

​

Bandwidth

Outbound bandwidth from the Bannerify CDN is included in every plan. You can embed generated assets in webpages, apps, and emails without paying an extra transfer fee.

​

Usage quota per plan

Each workspace comes with a monthly render allowance. When a render call succeeds, it consumes one credit from your plan’s quota. Usage is tracked per tenant. We compare the number of completed renders against your plan’s allowance on every request. Free workspaces can render up to 10 billable assets per day, with no carryover. If you need higher limits, reach out to support and we can adjust the quota for your workspace.

​

Rate limiting

Bannerify enforces burst protection on every API key to keep workloads stable. By default each key can issue up to 100 requests every 10 seconds with a refill rate of 10 requests per second. Free workspaces are also paced by the daily render cap above. When the limit is reached, the API responds with 429 and includes RateLimit-* headers so you know when to retry.

• REST endpoints (for example /v1/templates/createImage and /v1/templates/createPdf) use the same limiter configuration.
• Signed URL requests (/v1/templates/signedurl) share the limiter and will also return headers showing the current window.
• Internal automations and thumbnail previews respect the limit unless you have been granted a skip flag by the Bannerify team.

Enterprise customers can request custom thresholds to align with their throughput requirements.

​

Cache behaviour for signed URLs

Signed URL responses automatically cache the generated asset. When the same payload is requested again:

• If the asset exists in cache and nocache is not set, Bannerify returns it instantly and sets the Bannerify-Cache: HIT header.
• If the asset is missing or nocache=true, the renderer creates a fresh version, stores it, and serves it to the caller.
• The default cache lifetime is 1 hour. Purging or updating the template invalidates the cache key automatically.

Calling createImage or createPdf always renders a new asset and bypasses the cache.

​

Tips for staying within quota

• Reuse signed URLs when you need deterministic outputs from identical data.
• Use thumbnail previews for non-production QA—they do not count against your quota.
• Monitor usage and rate limit metrics from Dashboard → Activity and export logs if you need long-term audits.