What the interface provides
Send endpoint
A REST call or SMTP submission per message, with the recipient, template and variables. Responses tell you immediately whether the message was accepted.
Templates
Versioned templates per language, so the copy of a password reset can change without a deployment of the application.
Event webhooks
Delivered, bounced, complained: your application learns about it within seconds and can stop writing to dead addresses.
Suppression handling
Hard bounces and complaints are blocked automatically for your account, so a bug in your code cannot keep mailing them.
What the API will not do
Limits are part of the product. They protect every application that shares our sending infrastructure.
- No list uploads: the API accepts one recipient per call, tied to an event in your application.
- No marketing campaigns, even if they are sent one message at a time.
- No sending to addresses your users did not enter themselves.
- No continued sending to addresses that bounced or complained.
- No anonymous accounts: every account belongs to a named company with a reachable abuse contact.
Contact
For development teams, for recipients of an application mail and for blocklist operators:
Monitored on working days. Abuse reports have priority over everything else.