Get a receiving address
Create a managed address for your team without changing DNS, or connect your own receiving domain.
Incoming email.
Ready for your application.
Start without DNS. Get a managed email address for your team in one click, then route incoming messages straight into your application.
Choose what happens next
Match addresses with a pattern or regular expression. Forward to a webhook, store, or reject.
Build your reply workflow
Process email.received events, stripped reply text, and attachments.
An address without the DNS setup
Create a managed address such as support@your-team.in.zapsmtp.com. Use your own domain when you need it.
Routes that fit your workflow
Match incoming addresses by pattern or regex, then send to a webhook, store the message, or reject it.
Just the reply you need
Get reply text without the quoted thread, read +tags in addresses, and link replies to the email you sent.
Scan incoming messages
Spam scanning checks incoming mail before it enters your workflow.
Attachments with controlled access
Retrieve attachments through signed download links.
Delete on request
Delete stored inbound messages when handling a data deletion request.
Plan limits
API and SMTP are included in every plan. Free includes 3,000 emails per month, one domain, and three days of logs. Pro includes ten domains and 30 days of logs; Scale includes unlimited domains and 90 days of logs.
Compare plansGood to know
Verify your domain before production sending. Keep API keys and SMTP passwords on your backend. Delivery depends on content, reputation, authentication, and the receiving provider; an accepted request does not guarantee inbox placement.
Send your first email.
Your next email starts with a few lines of code.
Start building 3,000 emails / month free