Use case

Transactional email for SaaS

Password resets, receipts, and in-app notifications need to arrive in seconds, not sit in a marketing send queue. One API, a free tier that survives a real launch, and a delivery pipeline built for the emails your product depends on.

Send

One request, no queue to manage

POST an HTML body, a text body, or a template alias to /v1/emails and get a 202 back with an id in milliseconds. Pass an idempotency_key derived from your own event — an order id, a password-reset token — and network retries can never double-send.

curl -X POST https://api.euromail.dev/v1/emails \
  -H "X-EuroMail-Api-Key: em_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "[email protected]",
    "to": "[email protected]",
    "subject": "Reset your password",
    "html_body": "<a href=\"...\">Reset</a>",
    "idempotency_key": "pwreset-8814-a2"
  }'
202 Accepted  { "status": "queued" }
Confirmation

A webhook fires on delivered, bounced, complained, opened, and clicked, signed with HMAC-SHA256 in the X-EuroMail-Signature header so you can verify it came from EuroMail before trusting the payload. Free-form metadata you attach at send time is echoed back on every event, so correlating a webhook to your own order or user record is a lookup, not a join. Failed deliveries retry with exponential backoff before we give up and tell you.

Scale

A free tier that survives a real launch

The free plan includes 3,000 emails a month with the same delivery pipeline, deliverability tooling, and DPA as every paid tier — nothing about sending itself is gated behind an upgrade. A platform that sends on behalf of its own customers can move to Business or Enterprise and issue each one an isolated sub-account, with its own API keys, domains, and quota drawn from a shared pool, without a separate contract per customer.

Free tier
3,000 emails/mo
DPA
Every plan, including Free
Sub-accounts
Business/Enterprise plans
Idempotency
Same key, original result

Related

  • Transactional email

    One POST, a 202 response, and delivery tracked through queued, sending, and delivered.

  • Webhooks

    HMAC-signed delivery, bounce, and complaint events posted to your endpoint.

  • API keys & authentication

    Scoped keys per environment, so a leaked staging key can't touch production.