Frequently asked questions

An email delivery service: we send your transactional and bulk email so it reaches the inbox, and we handle DKIM, SPF, DMARC and reputation for you.

Of course! We are using great template renderer system called Jinja, which allows to implement any custom logic inside the email templates.

Three ways: a REST API, an SMTP relay, or our official Python SDK. Pick whatever fits your stack best.

Yes. We publish an official Terraform provider, so you can describe templates in code, keep them under version control, and ship them through CI/CD.

Yes. Subscribe an HTTPS endpoint to events like delivery, bounce, open and unsubscribe, and we'll POST a signed JSON payload in real time — no polling required. See the Webhooks documentation.

Yes, on paid plans. Point the MX of a subdomain — say inbound.yourdomain.com — at us, add routes for the addresses you care about, and every message that arrives is POSTed to your service as an inbound.received webhook, already parsed, with links to the raw .eml and each attachment. It is not a mailbox: nothing is kept for a human to read, it goes to your application. See the inbound documentation.

Two, and they behave differently. Your plan sets an hourly and a monthly volume, and a submission over either one is refused. Separately, every domain is paced by a warm-up ramp: it starts at 200 messages a day on every plan, free or paid, then roughly doubles from your busiest recent day as you keep sending, so a domain reaches high volume in about a week of real traffic. Going over the ramp is never an error — the mail is accepted and delivered a little later. See sending limits.

Every message is scored when we accept it, and each domain's overall pattern is watched — a large share of suspicious content, or a new domain sending far more than it ever has. Nothing is refused because of a single message. If a domain does cross the line, sending from it is stopped, everyone on the domain is emailed with the reason, and queued mail is held rather than deleted so it can be released if the block is lifted. Purchased and scraped recipient lists are the most common cause. See sending limits and anti-abuse.

All examples and documentation available Documentation and Examples

It depends on your plan: 7 days on free plans and 30 days on paid ones. Old data is cleared every 12 hours, so after a downgrade from a paid plan anything older than 7 days is removed within the next 12 hours.