Skip to main content

Email aliases built for deliberate automation.

Create and manage aliases with a REST API. React to incoming email with signed webhooks. Build email workflows without adding another noisy inbox.

REST / HMAC-SHA256 / annual access

API-first alias management

Create an alias
curl -X POST https://mailservr.app/api/addresses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address": "notifications", "domainId": "DOMAIN_ID"}'
List inbox threads
curl https://mailservr.app/api/emails \
  -H "Authorization: Bearer YOUR_API_KEY"
Webhook payload (email.received)
{
  "event": "email.received",
  "data": {
    "threadId": "thr_abc123",
    "from": "[email protected]",
    "to": "[email protected]",
    "subject": "Deployment successful",
    "receivedAt": "2026-02-13T10:30:00Z"
  }
}

Common developer workflows

CI/CD notification routing

Create one alias per repository or pipeline. Route GitHub, Vercel, and AWS alerts to categorized addresses. Triage by alias in the inbox instead of writing complex filter rules.

SaaS trial isolation

Spin up a temporary alias for each free trial. Use the API to create the alias, sign up, and delete the alias after the trial ends. No more trial spam in your real inbox.

Customer support routing

Give each client or ticket system a unique alias. All communication is organized by address. When the engagement ends, deactivate the alias.

Internal tool integration

Use webhooks to push incoming email events to Slack, Discord, or your own monitoring stack. React to email.received events in real time without polling.

Password manager alias generation

Connect Bitwarden to mailservr's SimpleLogin/Addy.io-compatible API. Aliases are auto-generated when creating new logins without leaving your password manager.

Developer plan comparison

CapabilityPlus (€20/year)Max (€50/year)
API keys110
Webhook endpointsNot includedUp to 5
Total aliases30500
Active aliases15200
Monthly send limit2002,000
Attachment storage1 GB10 GB
Password manager integrationYesYes

Developer FAQ

What authentication does the API use?

The API uses Bearer token authentication. Generate API keys from your dashboard settings. Plus includes 1 API key; Max includes up to 10.

Are webhook payloads signed?

Yes. Every webhook payload is signed with HMAC-SHA256. Your endpoint can verify the signature to ensure payloads are authentic and untampered.

What events do webhooks support?

Webhooks fire on email.received, email.sent, and thread.created events. Max supports up to 5 webhook endpoints with delivery logs.

Does mailservr work with Bitwarden?

Yes. mailservr implements the SimpleLogin and Addy.io alias generation protocols that Bitwarden can use with a custom server URL. 1Password's Masked Email integration does not currently accept a custom provider URL.

Start building with mailservr.

API access is available on Plus and Max, with clear published limits.