Rate limits

BosonWare has not published API rate limits for the BosonMail REST API. This page covers what is known about plan-level allowances, client-side limits enforced by the SDK, and defensive practices you can apply while sending at scale.

​

Plan outbound allowance

Each BosonMail inbox includes a monthly outbound allowance: If you need more outbound volume, BosonWare offers two options:

​

Client-side limits

The SDK enforces the following limits before any network request is made: These are hard limits. The SDK returns success: false immediately without calling the API.

​

Defensive practices

Since API rate limits are not published, design your integration to tolerate throttling and backpressure:

1. Limit concurrency: send emails sequentially or with a small concurrency pool (for example, 3-5 in parallel) rather than unbounded Promise.all.
2. Back off on server errors: if you receive HTTP 429 or 5xx responses, pause and retry with exponential backoff. The SDK does not retry automatically.
3. Queue large batches: use a job queue (Bull, Inngest, or a database-backed queue) instead of firing thousands of requests at once.
4. Monitor status, not just success: a success: true from sendEmail means the API accepted the message, not that it was delivered. Use getEmailStatus to track terminal outcomes.
5. Contact BosonWare for volume: if you plan to send more than a few thousand emails per month, reach out to support@bosonware.com to discuss allowances and infrastructure.

​

What the SDK does not enforce

The SDK does not implement:

• Per-second or per-minute rate limiting
• Automatic retries on 429 or 5xx
• Queueing or batching

These are application-level concerns. See Production best practices for patterns.

​

Next steps