Skip to content

Reference

Rate limits, quotas, and usage

How much you can send, how fast, and how to check where you stand.

Rate limits

Each API key can make 10 requests a second. Responses to authenticated requests carry these headers:

HeaderMeaning
ratelimit-limitRequests allowed per window.
ratelimit-remainingRequests left in the current window.
ratelimit-resetSeconds until the window resets.
retry-afterOn a 429, seconds to wait before retrying.

Past the limit, requests fail with 429 rate_limit_exceeded. Wait for retry-after and try again, or use batch sends to send more per request.

Monthly sends

Each plan includes a monthly allowance, shared by mailbox mail, SMTP relay, and the API. Every email counts once, however many recipients it has. Past the allowance, sending continues and extra sends are billed per 1,000, up to a cap of twice the allowance by default:

PlanIncluded sendsSending stops at
Mini15K30K
Business75K150K
Enterprise250K500K

At the cap, sends fail with 429 monthly_quota_exceeded until the next billing period. If a payment is overdue, sending is held to the included allowance. See pricing for per-1,000 rates.

Size limits

LimitValue
Recipients per email (to + cc + bcc)50
Attachments per email, total40 MB
Emails per batch100
Batch request body20 MB
Scheduling window30 days
Idempotency key lifetime24 hours

Paused sending

To protect deliverability for everyone, Chebu watches bounce and complaint rates over the last 7 days once a workspace has sent at least 200 emails. At a 10% bounce rate or a 0.5% complaint rate, sending pauses until our team reviews it, and requests fail with 403 workspace_paused. Keeping lists clean and honoring the suppression list keeps you well below that.

Check usage

GET/usage
Request
curl https://api.chebu.io/usage \
  -H "Authorization: Bearer $CHEBU_API_KEY"
JSON