Skip to content

Rate Limits & Quotas

BinderyPress enforces both rate limits (requests per time window) and monthly quotas (total renders per billing period) based on your team’s plan.

API-key requests count toward your plan’s rate limits and monthly quota. In the Bindery Press app:

  • Printing counts toward your monthly quota, just like an API render.
  • On-screen previews (designer, print preview, AI wizard) are free and never counted. On the free Dev plan they carry a PREVIEW — FREE PLAN watermark.
  • App renders share a separate per-team limit of 20 per minute and 200 per hour, so heavy API traffic never locks you out of the designer.
Plan Monthly Renders Rate (per min) Rate (per hour) At the quota
Dev (free) 100 10 100 Renders stop
Small 1,500 60 1,000 20% allowance, then renders stop
Big 15,000 300 5,000 Renders never stop
Enterprise Unlimited 600 10,000 Renders never stop

Need a volume between Small and Big? Talk to us.

Every plan can render a batch: a list in data on a single-label template, one label per item.

Plan PDF, HTML ZPL, PNG
Dev 10 10
Small 100 100
Big, Enterprise 250 100

Each label counts as one render toward the monthly quota; the request counts once toward the rate limit. A longer list is refused with 400 BATCH_TOO_LARGE and nothing is rendered or counted.

The Dev plan holds up to 10 templates, not counting the trash. At the limit, creating, duplicating, restoring from the trash and AI generation are refused until you delete a template or upgrade. Small, Big and Enterprise have no template limit.

A team that moves back to Dev with more than 10 templates keeps all of them, and they keep rendering; it cannot add more until it is below the limit.

Rate limits are enforced per team on API-key requests to the /v1/render endpoint. They count requests: a batch is one request, however many labels it holds. Every successful API-key response includes rate limit headers:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 58
X-RateLimit-Reset: 1711843260

When the rate limit is exceeded, the API returns:

{
"error": "Rate limit exceeded",
"code": "RATE_LIMITED"
}

Status: 429 Too Many Requests Header: Retry-After: <seconds>

Each plan includes a monthly render quota. Live API-key renders and prints from the Bindery Press app count against it, one per label: a batch of 50 counts 50. Test-key renders and on-screen previews never count.

A batch is counted all or nothing: if fewer renders are left this month than the batch has items, the whole batch is refused with 429 QUOTA_EXCEEDED (the message says how many are left) and nothing is counted. On Small, a batch may use the allowance up to the stop point exactly.

Plan What happens
Dev Renders are refused with 429 QUOTA_EXCEEDED once the 100 renders are used.
Small When the quota is reached, the team owner gets an email, and renders continue for a further 20% of the quota (300 more: up to 1,800 renders). After that, renders are refused with 429 QUOTA_EXCEEDED and the owner gets a second email. Each email is sent at most once a month.
Big, Enterprise Renders never stop.

When renders stop:

{
"error": "Monthly render quota used up. Renders resume on the 1st of next month (UTC), or upgrade your plan: https://app.binderypress.dev/billing",
"code": "QUOTA_EXCEEDED",
"details": {
"usage": { "current": 1800, "limit": 1500, "stopAt": 1800 },
"upgradeUrl": "https://app.binderypress.dev/billing"
}
}

Status: 429 Too Many Requests

details.usage.limit is your quota and details.usage.stopAt is where renders stop (the same as the quota on Dev). A refused render is not counted.

Use the GET /v1/usage endpoint to check your current usage and remaining quota at any time.

Quotas reset at the beginning of each calendar month (UTC). The reset is automatic — no action required.