Production ready transactional email infrastructure

Transactional email API: receipts, alerts and codes from your own domain

Verify a domain, paste the records, and send. Add one more record and the same domain receives: every address on it becomes an inbox you read by API and webhook, with replies linked to the email they answer.

Watch it work, start to finish

Start by setting up your account and domain. Then pick your path: the complete guide if you write the code, or the AI walkthrough if your assistant does. Every step is one you can do with a free test key.

Start here: set up in the console

1 minute 24 seconds, with narration and English captions.

Developers: the complete guide

2 minutes 44 seconds, with narration and English captions.

Building with AI: no code to write

2 minutes 17 seconds, with narration and English captions.

The account, domain and key in these videos are examples.

What you get

DKIM generated for you

Add a domain and Woyra generates its keys and shows the exact DNS records to paste. It checks them for you and tells you when sending is live.

Bounces and complaints handled

A hard bounce or a spam complaint suppresses the address on your account, and you receive an email.undelivered or email.complained webhook. Nobody is emailed twice by mistake.

Signed unsubscribe

List-Unsubscribe headers, signed so that a link cannot be forged, on every message you mark as marketing. The recipient is suppressed the moment they click.

Receives on the same domain

Point the MX record at Woyra and every address on the domain receives. Each message is stored on your account, delivered as an email.received webhook with its text and attachments, and linked to the email it replies to. No routing rules, no separate product.

The call

Send from a verified domain, then follow the message through delivery events.

curl -X POST https://api.woyra.io/v1/emails \
  -H "Authorization: Bearer $WOYRA_KEY" \
  -H 'Idempotency-Key: receipt-4821' \
  -H 'Content-Type: application/json' \
  -d '{
    "from": "receipts@yourdomain.com",
    "to": "alex@example.com",
    "subject": "Your receipt for order 4821",
    "text": "Thank you. Your order is confirmed."
  }'

Reference price: Compare on reliability, tooling and workflow. Full list on the pricing page.

Questions

How is production email billed?

Production usage is metered and controlled through your Woyra account. The console shows your active service, usage and billing status before you send.

Do I have to set up DKIM and SPF myself?

Woyra generates the DKIM keys and shows you the records, including SPF and a DMARC suggestion. Paste them at your DNS provider and click verify.

What happens when an email bounces?

A hard bounce suppresses the address on your account and sends you an email.undelivered webhook. A later send to that address is recorded as suppressed and not charged.

Can I send from a test key?

Yes. A test key accepts every request, charges nothing and skips DNS verification, so you can build the whole flow before your domain is live.

Can I receive email too?

Yes, on the same domain. Add the MX record Woyra gives you and every address on the domain receives: support@, replies to receipts, anything. Each message arrives as an email.received webhook and is readable under /v1/emails/inbound, with attachments and a link to the email it replies to.

Do replies stay in one conversation?

Yes. A reply to something you sent joins its thread, and answering it is one call with in_reply_to: the addresses and subject come from the email being answered, and the mail carries the headers that keep it in the same thread in Gmail and Outlook. One endpoint reads the whole exchange.

Email by country

For teams worldwide, with a dedicated set of setup guides for African markets.