Skip to main content

Overview

Rate limits protect the API from abuse and ensure fair usage for all users. Limits are applied per organization using an in-memory sliding window.

API Request Limits

Need higher limits? Contact us to discuss your volume requirements.

Email Sending

Unosend uses a credit-based system. 1 credit = 1 email. Contact us for pricing and volume details.
  • No subscription — buy credits when you need them
  • Email size limit: 15 MB (headers + body + inline images + attachments)

Domain Sending Limit

There is a global daily limit of 200,000 emails per sender domain across all plans. This protects shared infrastructure and ensures deliverability.

Domain Creation Rate Limit

All plans include unlimited domains. To prevent abuse, domain creation is rate limited to 10 domains per hour per organization. This is a velocity cap — there is no limit on the total number of domains you can add. If you exceed this limit, the API returns 429 Too Many Requests. Wait and retry after a few minutes.

Rate Limit Headers

Every API response includes headers to help you track your rate limit status:

Example Response Headers

response-headers.txt

Check Current Usage

You can check your current rate limit status with any API request by inspecting the response headers, or use the usage endpoint:
Terminal

Response

response.json

Handling Rate Limits

When you exceed the rate limit, the API returns a 429 Too Many Requests response:
rate-limit-response.json

Implementing Retry Logic

Exponential Backoff

For robust retry logic, use exponential backoff with jitter to avoid thundering herd:
exponential-backoff.ts

Queue Pattern for Bulk Sending

For sending many emails, use a queue with rate limiting to stay within limits:
rate-limited-queue.ts
For bulk sending, consider using the /emails/batch endpoint which allows up to 100 emails per request, significantly reducing API calls.

Best Practices

1

Monitor rate limit headers

Check X-RateLimit-Remaining and slow down before hitting limits.
2

Use batch endpoints

Send multiple emails in one request using POST /emails/batch to reduce API calls.
3

Implement queuing

Queue emails during high-traffic periods and process them at a controlled rate.
4

Use webhooks instead of polling

Instead of polling for status, use webhooks to receive delivery updates asynchronously.
5

Cache responses when possible

Cache responses from endpoints like GET /domains to reduce unnecessary requests.

Need Higher Limits?

If you need higher rate limits for your use case, upgrade your plan or contact us for Enterprise options with custom limits.