API Reseller
Email API
Transactional email with template management, domain authentication and per-message delivery tracking, including the bounce and complaint handling that keeps a sending domain in good standing.
What you get
- Template management with variable substitution
- SPF, DKIM and DMARC domain authentication
- Delivery, open and bounce tracking
- Attachment support
- Automatic suppression of bounced and complained addresses
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Domain
- SPF and DKIM must be configured on your sending domain before go-live.
- Delivery
- Asynchronous. Bounces and complaints are reported by webhook.
- Webhook
- Signed, with replay protection. Retried until your endpoint returns 2xx.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About email api
Why do I need SPF and DKIM before going live?
Without them, mail sent on your behalf fails authentication at the receiving end and lands in spam or is rejected outright. Configuring both is what makes your domain the verified sender rather than an impersonation attempt.
How do I know a message actually arrived?
By webhook. Bounces and complaints are reported back, and a hard bounce should suppress that address in your own system — continuing to send to a dead address damages the sending reputation of your whole domain.