Trust tiers & sandbox
New Irisend accounts start in a sandbox and earn higher limits from their delivery record. See the four tiers, sandbox rules, and how to move up a tier.
Why new accounts start in a sandbox
Irisend sends through a shared reputation. One account mailing a purchased list can hurt delivery for everyone before any automatic safeguard reacts, so a new account starts small and earns wider limits from its own delivery record.
The sandbox is not a paywall. Limits never depend on payment: paying does not move you up a tier, and a stolen card cannot buy one. What moves you up is verifying who you are and then sending mail that people want.
The four tiers
Every team has exactly one tier. Daily and monthly caps count recipients (to, cc and bcc), in UTC. Where a tier shows your plan's limit, your plan (or the early-access cap) is the only cap that applies.
| Limit | Sandbox | New | Established | Trusted |
|---|---|---|---|---|
| Emails per day | 50 | 100 | Your plan's limit | Your plan's limit |
| Emails per month | 1,000 | 1,000 | Your plan's limit | Your plan's limit |
| Recipients per request | 50 | 50 | No tier limit | No tier limit |
| Who you can send to | Your verified email, your verified domains, SES simulator | Anyone | Anyone | Anyone |
| Sending domains | 2 | 2 | 20 | 100 |
| New domains per day | 2 | 2 | 5 | 20 |
| Click tracking | Off | Off | Available | Available |
| Attachments | Safe types only | Safe types only | Any allowed type | Any allowed type |
The per-request limit applies to the whole request: one send, an entire POST /emails/batch, one SMTP DATA transaction, an MCP call, or a broadcast's recipient count. Safe attachment types are pdf, png, jpg, jpeg, gif, webp, txt, csv and ics. The same limits apply on every transport: the REST API, SMTP, MCP and broadcasts.
What the sandbox can send to
Until your account leaves the sandbox you can mail three kinds of address, and nothing else.
- Your own verified email address, and the verified email address of any member of your team.
- Any address on one of your verified domains.
- The Amazon SES mailbox simulator, so you can test an integration on day one:
[email protected],[email protected],[email protected],[email protected]and[email protected].
Sending to any other recipient is refused before anything is queued, with a 403 validation_error. The message names the first recipient that is not allowed:
curl -X POST https://api.irisend.com/emails \
-H "Authorization: Bearer $IRISEND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "Acme <[email protected]>",
"to": ["[email protected]"],
"subject": "Hello",
"html": "<p>Hi!</p>"
}'{
"statusCode": 403,
"name": "validation_error",
"message": "You can only send to your own verified address, to addresses on your verified domains, and to the SES mailbox simulator (e.g. [email protected]) until your account leaves sandbox. `[email protected]` is not one of them. Your account is in sandbox mode. Verify your email address and a sending domain and it leaves sandbox automatically; see https://irisend.com/docs/trust-tiers."
}SMTP clients get a 550 reply carrying the same text. A broadcast whose audience holds an address outside the allow-list is refused as a whole while you are in the sandbox. See Errors for the full error catalogue.
Leaving the sandbox
You leave the sandbox automatically once your account has done two things. There is no form to fill in and nothing to request.
- Verify your email address — the one you signed up with, using the link we sent.
- Verify a sending domain — add the DNS records from Domains and wait for the status to turn
verified.
Promotion is checked every hour, so it can take up to an hour after your domain verifies. The account must also be active, have no open safety flag (for example a bounce or complaint warning on one of your domains), and must not have been moved back for poor delivery results. Leaving the sandbox puts you in the new tier, which can send to anyone.
From new to established
The new tier is a probation period. You move up to established automatically once all of these hold, measured over the time you have spent in the new tier:
- at least 14 days in the new tier;
- at least 200 delivered emails;
- a hard bounce rate under 2 %;
- a spam complaint rate under 0.05 %;
- no open safety flag.
These thresholds sit at about half of what mailbox providers and AWS enforce (hard bounces 5 %, complaints 0.1 %), on purpose. The same record can also move you down: with at least 100 sends in the last 30 days, a hard bounce rate of 3 % or more, or a complaint rate of 0.075 % or more, drops the account one tier. A team that was demoted this way stays down until our team reviews it; contact support.
The suppression and bounce handling that keeps bad addresses off your list also keeps your rates low. Sending only to people who asked for your mail is the surest route up.
Good to know
A few rules that are easy to miss.
- Payment never changes your tier. A paid plan raises your plan limit, but the tier caps above still apply first.
- A sub-account is capped at its parent's tier. It can never outrank the team that bills for it, and it follows the parent when the parent moves.
- Trusted is set by hand. It is the tier for established senders with high-volume or unusual needs. Ask support from the dashboard's Support page or at [email protected], say what you send and to whom, and we review it. Nothing promotes you to trusted automatically.
- Existing teams are not affected retroactively. Teams created before tiers existed start as established.
Where to see your tier
Your current tier, its limits and the next steps are on the dashboard Usage page.
Open Usage in the dashboard. It shows your tier, the daily and monthly bars measured against the cap that actually applies to you, and a checklist of what is still missing for the next tier, such as the number of days or delivered emails so far. Questions about a tier decision? Write to [email protected].