Email sending limits explained: 50 a day per project, and why
thelastapi caps transactional email at 50 sends per project per UTC day to protect sender reputation, resetting daily with options for larger volume.
On this page 7 sections
- What are the email sending limits across each feature?
- Why is there a 50 emails per day limit on project addresses?
- What happens when you hit the daily limit?
- How to handle bounces, complaints, and paused sending
- How to send more: custom mailboxes and marketing broadcasts
- How to inspect usage and send transactional mail safely
- FAQ
thelastapi limits transactional email to 50 emails per project per UTC day across all its mailboxes on the default project domain. This daily ceiling keeps shared mail domains off blocklists, prevents runaway loops in automated code, and guarantees clean deliverability for every project. When your business needs to send customer communications at higher scale, you can add custom domain mailboxes or set up marketing broadcasts with dedicated warmup schedules.
Understanding how email sending limits work across transactional mail, personal agent inboxes, custom domain mailboxes, and newsletters helps you design reliable notification flows. You can read more about how setup works in the Email docs.
What are the email sending limits across each feature?
Different types of email have different deliverability profiles, so thelastapi separates transactional code triggers, inbox conversations, and newsletter campaigns into distinct tiers.
Every project email resource sends from an assigned address at <mailbox>@<slug>.vibiz.app (info@<slug>.vibiz.app by default), aligned automatically with SPF, DKIM, and DMARC. Because all projects on that shared infrastructure rely on clean sender standing, strict daily quotas apply.
| Sending mode | From address | Daily limit (UTC) | Notes & thresholds |
|---|---|---|---|
| Project transactional | <mailbox>@<slug>.vibiz.app | 50 emails per project | 1 recipient per send; failed sends do not count |
| Personal agent inbox | <name>@agent.vibiz.app | 20 emails per account | Single shared domain inbox; sends and receives |
| Custom domain mailbox | hello@yourcompany.com | 200 per mailbox / 1,000 per account | Up to 50 recipients per send; 20 MB message limit |
| Email forwarding | hello@yourcompany.com | 500 forwards per domain | Max 30 forwards per sender per hour |
| Marketing broadcasts | hello@news.<slug>.vibiz.app or news.yourcompany.com | 500 on day 1 (doubles daily to 100,000) | Pauses at >2.5% bounces or >0.08% spam complaints |
| Broadcast tests | Project owners | 20 tests per day | Sent to project owners or up to 5 addresses |
Each transactional send costs approximately $0.00013 ($0.0001 plus 30%) deducted from your account credits, and failed sends record nothing.
Why is there a 50 emails per day limit on project addresses?
When you create a project and add the email resource, your app can immediately deliver order confirmations, password reset codes, and sign-in links without configuring DNS records. You can explore this workflow in Send transactional email from your app without touching DNS.
A 50-send daily limit on these project addresses serves three specific engineering purposes:
- Protecting domain reputation. Transactional addresses use the
<slug>.vibiz.appnamespace. If an automated script or compromised key begins spamming thousands of unverified addresses, major inbox providers like Gmail and Yahoo will penalize the underlying domain. Restricting each project to 50 messages per day confines blast radiuses and maintains high inbox placement for everyone. - Preventing infinite automation loops. Bugs happen. A webhook re-triggering itself on status updates or an unhandled recursion in an async worker can trigger thousands of outbound calls in seconds. A strict ceiling of 50 sends halts runaway billing and inbox flooding before thousands of emails leave your project.
- Encouraging proper protocol separation. Transactional mail should never be mixed with outbound marketing. Transactional notifications need instantaneous delivery and absolute inbox trust. By capping
<slug>.vibiz.appat 50 emails a day, teams are prevented from treating transactional endpoints as bulk newsletter systems.
What happens when you hit the daily limit?
When a project attempts to send its 51st transactional email within a single UTC day, the API refuses the request immediately.
The server returns an HTTP status code 429 Too Many Requests with a structured JSON error body:
{
"error": {
"code": "rate_limited",
"message": "Daily sending limit reached.",
"details": {
"limit": 50,
"resets_at": "2026-04-01T00:00:00.000Z"
}
}
}The resets_at field tells your backend the exact ISO timestamp when the UTC day rolls over and sending credits refresh. Because failed sends do not decrement your daily quota or bill credits, a 429 error does not consume a send.
When implementing transactional dispatch in an app, always wrap your send calls to handle rate_limited cleanly:
import { vibiz } from '@vibiz/app';
try {
await vibiz.email.send({
to: 'ana@example.com',
subject: 'Your order is ready',
text: 'Pick it up any time today.',
from: 'orders',
reply_to: 'owner@example.com',
});
} catch (err: any) {
if (err.code === 'rate_limited') {
console.error(`Daily limit of ${err.details.limit} reached. Resets at ${err.details.resets_at}`);
} else if (err.code === 'dependency_not_ready') {
console.error('Email domain is still verifying. Try again in a few minutes.');
}
}To see how this pattern fits into customer onboarding, read Send a welcome email from a Next.js app.
How to handle bounces, complaints, and paused sending
Limits protect volume, but delivery quality determines whether an address remains active. If your transactional mail generates too many hard bounces (invalid inboxes) or recipients flag messages as spam, the project enters a sending_paused state.
When sending is paused, calls to /actions/email.send fail with status 403 Forbidden and error code forbidden with sending_paused. The project owner must clean the contact list and contact support to re-enable sending.
To keep your sending reputation healthy:
- Always provide an
Idempotency-Keyheader on API requests so retried HTTP connections cannot send duplicate emails to the same recipient. - Require valid email formatting before calling the API.
- Never use purchased, scraped, or unverified contact lists.
- Set a valid
reply_toaddress on transactional sends, since the<slug>.vibiz.appdomain does not receive inbound mail.
You can inspect the technical mechanisms behind authentication headers in DKIM, SPF and DMARC: email deliverability basics, done for you.
How to send more: custom mailboxes and marketing broadcasts
When your business expands beyond 50 transactional emails a day, you have two native paths depending on the kind of mail you are sending.
1. Custom domain mailboxes for direct team correspondence
For personalized customer conversations, support inboxes, or sales replies from your own domain (hello@yourcompany.com), create a mailbox:
vibiz email mailbox add hello@sellshelf.app --name "Sell Shelf"
vibiz email dns sellshelf.app --checkEach custom mailbox can send up to 200 messages per UTC day, with an overall account limit of 1,000 messages per day across all mailboxes. Messages sent via custom mailboxes can include up to 50 recipients per send and attachments up to 15 MB (with a total message ceiling of 20 MB).
2. Marketing broadcasts and automations for audience scale
If you are sending newsletters, onboarding campaigns, or product announcements, use the dedicated marketing resource. Marketing email is completely isolated from transactional mail, running from its own subdomain (hello@news.<slug>.vibiz.app or news.yourcompany.com) with its own reputation.
Initialize marketing email from the CLI:
vibiz email setup
vibiz email settings set --postal-address "1 Main St, Springfield, IL 62701, USA"Marketing broadcasts bypass the 50-send transactional limit using an automated domain warmup schedule:
- Starting limit: 500 marketing emails on the first sending day.
- Warmup scaling: The daily limit doubles with each clean sending day (from 500 to 1,000, 2,000, 4,000, and up to 100,000).
- Automated safeguards: If hard bounces exceed 2.5% or spam complaints exceed 0.08%, the broadcast pauses automatically to protect your domain standing.
- Cost: Billed at $0.001 per sent contact ($1 per 1,000) from account credits.
How to inspect usage and send transactional mail safely
You can check whether your project is nearing its 50-email daily ceiling using the CLI or standard HTTP headers.
When you send an email over HTTP, the response body details your current usage against the limit:
curl https://thelastapi.dev/v1/projects/prj_123/actions/email.send \
-H "Authorization: Bearer $VIBIZ_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: welcome-u_123" \
-d '{"input":{"to":"ana@example.com","subject":"Welcome","text":"Hi Ana","from":"hello"}}'The output payload returns your project's current status and daily count:
{
"output": {
"id": "msg_987",
"from": "hello@acme-bakery.vibiz.app",
"to": "ana@example.com",
"status": "sent"
},
"usage": {
"used": 1,
"limit": 50,
"resets_at": "2026-04-01T00:00:00.000Z"
}
}You can also check mailbox usage across your account using the CLI:
vibiz email mailboxes --jsonBy keeping transactional volume within the 50-per-day boundary and shifting audience updates to broadcasts or mailboxes, your applications maintain reliable deliverability across all providers.
Create your account at thelastapi.dev/start to start sending transactional and marketing emails with thelastapi.
Frequently asked questions
When does the daily email sending limit reset?
The limit resets every day at 00:00:00 UTC. The API response includes a `resets_at` ISO timestamp showing when your 50 sends refresh.
Do failed sends count against my 50 emails per day limit?
No. A send that fails due to validation errors, an unverified domain, or rate limiting does not decrement your daily quota, and no credits are billed.
Can I send an email to multiple recipients on the transactional endpoint?
No. The transactional `email.send` endpoint accepts only one address in the `to` field per request. Custom domain mailboxes, by contrast, support up to 50 recipients per send.
What happens if my marketing broadcast exceeds my current daily marketing limit?
The broadcast will dispatch up to your available limit for the day and queue the remaining contacts with `waiting: { reason: "daily_limit" }`, sending the rest over subsequent days as your reputation warms up.