WoyraDocs
Get an API key

Receive email on your own domain

One record, and every address on the domain receives. No destinations, no routing rules, no second product.

About 6 minutes · Every example runs against a test key, which costs nothing.

Add the MX record

A domain you already verified for sending is listed with one more record: an MX pointing at Woyra. Publish it and support@, receipts@ and every other address on the domain start receiving. The record is optional, so a domain whose mail already goes elsewhere is left alone.

Read what arrives

Each message is stored on your account with its text, its HTML, its headers, the provider’s authentication verdicts, and its attachments. It also reaches you as a webhook the moment it lands.

The email.received event
{
  "type": "email.received",
  "data": {
    "email_id": "inb_01J...",
    "thread_id": "email_01J...",
    "from": "alex@example.com",
    "to": "support@yourdomain.com",
    "subject": "Re: Your order 4821",
    "text": "Can you deliver after 5pm?",
    "in_reply_to": "email_01J...",
    "attachments": [
      {"id": "att_01J...", "filename": "photo.jpg", "content_type": "image/jpeg", "size_bytes": 84021}
    ]
  }
}

The webhook carries the first ten thousand characters of the text; the rest, the HTML and the files are one GET away. A webhook that carries a whole newsletter is a webhook that times out.

Replies come back linked

When the message answers something you sent, in_reply_to names that email and thread_id names the conversation. Your application knows which order the customer is asking about without parsing the subject line.

Answer from the same place

curl -X POST https://api.woyra.io/v1/emails \
  -H "Authorization: Bearer $WOYRA_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: reply-4821' \
  -d '{"in_reply_to": "inb_01J...", "text": "After five is fine."}'

The addresses and the subject come from the message being answered, so a reply is the id and the words. The mail goes out carrying In-Reply-To and References, which is what keeps it in the same conversation in Gmail and Outlook, and it joins the same thread on your account.

The whole exchange, in the order it happened
curl https://api.woyra.io/v1/emails/threads/email_01J... \
  -H "Authorization: Bearer $WOYRA_KEY"
Only a verified domain receivesWhatever an MX record says. Proving DNS control is what stops one customer registering another’s domain and reading their mail.

Questions

Is this a mailbox I can log into?

No, and deliberately. It is an inbox by API and webhook: the right shape for support tickets, reply-to-comment, and order confirmations by reply. A mailbox with folders for a human to read is a different product.

What happens to spam and viruses?

The receiving provider’s verdicts for SPF, DKIM, DMARC and spam are on every message so you can decide. A message that fails the virus scan is refused before it is read at all.

How large can a received message be?

Up to 40 MB, the limit of the receiving provider, attachments included.

Can two accounts receive the same message?

Yes, when it was addressed to verified domains on both. Each gets its own copy, and a provider retry never stores it twice.

Next

Get a test key and run any of this in about ninety seconds.