Skip to content
My Beast
Cart
Developer docsMenu

Mail · Getting started

Email API

Send your app's transactional email with one HTTPS request: order confirmations, password resets, receipts. JSON in, JSON out, from your own domain.

With the Email API you can:

  • send email from your own domain, signed with DKIM and covered by SPF and DMARC,
  • see what happened to every email and every recipient: queued, sent, delivered, bounced and so on,
  • get a webhook when an email is delivered, bounces or is marked as spam,
  • stop sending to addresses that bounce or complain, automatically.

It's a REST API only: there's no SMTP server to connect to. Any language that can make an HTTPS request can use it, so there's no library to install.

Send your first email

One request sends an email. Put your API key in an environment variable called MYBEAST_API_KEY and run:

curl -X POST https://services.my-beast.com/mail/api/email/v1/emails \
  -H "Authorization: Bearer $MYBEAST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme <hello@acme.com>",
    "to": ["customer@example.com"],
    "subject": "Your order has shipped",
    "html": "<p>Your order is on its way.</p>"
  }'
Response
{
  "id": "em_01JA2Q8ZK4T9W6",
  "status": "queued"
}

The response comes back as soon as the email is accepted. Before this works you need an API key and a verified sending domain: the quickstart takes you through both.

Basics

Base URLhttps://services.my-beast.com/mail/api/email/v1, over HTTPS only
AuthenticationAuthorization: Bearer mb_live_… on every request; a test inbox's mb_test_… key keeps the email instead of sending it. See Authentication.
FormatJSON in UTF-8. Requests with a body send Content-Type: application/json. Fields or query parameters the API doesn't know are refused, so typos don't go unnoticed.
SuccessEvery successful request returns 200 OK. Errors are described in Errors and limits.
IDsStrings with a prefix: em_ for emails, dom_ for domains, wh_ for webhooks. Store them as they are; don't rely on their length or format.
TimestampsISO 8601 in UTC, like 2026-10-09T09:14:03Z.
ListsNewest first, 20 at a time by default. See Pagination.

Plans and limits

Plans differ in how many sending domains, emails, API keys and days of delivery logs they include. Each plan is sold per month and invoiced 12 months in advance; prices are on the Email API plans page.

Loading the plans…

Every plan includes the full REST API, webhooks, SPF, DKIM and DMARC for your domains, the automatic suppression list and email support. The limits that are the same on every plan, such as 10 requests a second, are listed under Limits.

Explore the docs

QuickstartFrom an API key to a delivered email, step by step.Sending domainsThe DNS records to create, and how verification works.WebhooksEvents, payloads, signatures and retries.Bounces and suppressionsWhy some addresses stop receiving your email.Errors and limitsError types, rate limits, idempotency and pagination.API referenceEvery endpoint, field and response.