MailerSend · Rate Limits

Mailersend Rate Limits

MailerSend publishes two independent throttles on api.mailersend.com/v1: a per-minute rate limit that varies by endpoint, and a per-account daily request quota that varies by plan. Both surface as HTTP 429 and both are signalled in response headers on every request, so an agent can read remaining budget without waiting to be rejected.

Mailersend Rate Limits is the machine-readable rate-limit profile for MailerSend on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, message_rate_limit, and message_quota.

Tagged areas include Email, Transactional, SMS, Templates, and API.

5 Limits Throttle: 429
EmailTransactionalSMSTemplatesAPIRate LimitingQuotasThrottling

Limits

General API requests account
requests
60
Email send account
requests
120
Bulk email send account
requests
10
Activity account
requests
10
SMTP account
requests
120

Policies

Retry-After
On 429 the client must wait the number of seconds given in the retry-after header before retrying; MailerSend documents exponential backoff with jitter as the recommended client behaviour.
Avoid failed validation
MailerSend advises against repeating requests that fail 422 validation, as they consume quota.
Use bulk endpoint
High-volume senders are directed to POST /v1/bulk-email rather than looping POST /v1/email.

Sources