Sending limits
New accounts start with an hourly and a daily sending limit. The limits rise automatically as your account builds a healthy sending history.
How they work
- There are two limits: per hour and per day. The hourly limit counts the emails sent in each clock hour, and the daily limit those sent in each calendar day, both in UTC.
- Each recipient counts as one email: a message to 3 recipients counts as 3.
- The limits apply to your whole account: emails sent through the API and through SMTP count together.
- They're separate from your plan's monthly quota (codes
1417and1418). The quota sets how many emails you can send in the month; the sending limits set how fast you can send them. - The values depend on each account and change over time, so we don't publish them.
When you reach a limit
API
The sending endpoints answer with HTTP 429 and code 1421:
HTTP/1.1 429 Too Many Requests
Retry-After: 1260
Content-Type: application/json{
"status": "error",
"error": {
"code": "1421",
"message": "Sending limit reached."
}
}Retry-After gives the number of seconds to wait before sending again. The request isn't queued: your application has to send it again once that time has passed.
SMTP
The server answers with a temporary reply:
451 4.7.1 … Email deferred because the hourly sending limit of N emails was reached. Please retry later.The message wasn't accepted: send it again later. The text says whether the hourly or the daily limit was reached. See SMTP errors.
A single message above the limit
If one message has more recipients than your hourly or daily limit, waiting won't help: the API answers with HTTP 400 and code 1422, and SMTP rejects it with message exceeds send limit. Split it into messages with fewer recipients.
Bulk sending from day one
If you need to send in bulk from the start (moving from another provider, a launch, a newsletter to your whole list…), contact support before sending. Open a ticket from Support in the client panel, tell us the volume you expect, and we'll adjust your limits.
Tips
The limits rise with healthy sending, so:
- Spread large sends over time instead of sending everything at once.
- In your code, respect
Retry-Afterand retry SMTP4xxreplies later, with growing pauses. - Keep your lists clean: validate addresses before sending and stop sending to those that bounce.
- Send only to people who expect your emails, so complaints stay low.
See also
- Errors → /api-reference/errors
- SMTP errors → /smtp/errors
- Code examples → /guides/code-examples
