Introduction

emitd is transactional email as a plain HTTPS API — send from any language in a single request. SDKs for nine languages and a CLI exist when you want typed clients, but you never need one.

Every request authenticates with an API key as a Bearer token and talks to https://api.emitd.com. emitd validates the payload, rate-limits per tenant, checks your suppression list, and hands the message to AWS SES from the edge — then streams delivery, bounce, and complaint events to your signed webhooks.

curl https://api.emitd.com/v1/email \
  -H "Authorization: Bearer $EMITD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "you@yourdomain.com",
    "to": ["ada@lovelace.io"],
    "subject": "Welcome to Acme",
    "html_body": "<h1>You are in.</h1>"
  }'

You'll get a 202 with a message_id and watch it move in your activity feed.

What you getCopy Anchor Link

• One endpoint, one shape. POST /v1/email with a JSON body — plus batch, scheduling, templates, and attachments when you need them.
• Asynchronous by design. Sends return 202 immediately; delivery, bounce, and complaint events arrive on your webhooks, signed with HMAC.
• Honest limits. Per-minute burst limits and plan quotas are documented up front, enforced at the edge, and refunded when a send is rejected.
• Machine-readable. The full OpenAPI spec is published, llms.txt is a compact reference for model context windows, and a native MCP endpoint gives agents the same power.

Where to go nextCopy Anchor Link