For developers

Email aliases with a real API

Documented REST API. Open-source MCP server. OpenAPI 3.1 spec for SDK generation. Bearer-token auth. Custom domains with programmatic DNS verification. Built for the tooling you already use.

Get an API keyRead the API docs

API keys are a Premium feature ($4/mo, 7-day free trial). The free tier covers manual alias management from the dashboard.

What developers actually get

  • Documented REST API

    List, create, update, and disable aliases via plain HTTP. Bearer-token auth with `ea_live_…` keys minted from the dashboard. OpenAPI 3.1 spec for SDK generation and ChatGPT Custom GPT imports.

  • Open-source MCP server

    Native Model Context Protocol server lets Claude Desktop, Cursor, Zed, Cline, and any MCP-compatible client manage aliases conversationally. "Disable the amazon alias" actually works.

  • Bulk alias generation

    Loop POST /api/aliases for marketplace listings, security testing, per-tenant signups, or A/B email-flow testing. Each alias is independent — disable one without affecting the rest.

  • Custom domains with DNS

    Add up to 5 of your own domains, verify SPF/DKIM/DMARC programmatically, and mint aliases on whatever local-part scheme your tooling expects.

Quick start

Five-minute path from signup to first programmatic alias.

  1. 1

    Create an API key

    Sign up (or sign in) and head to Settings → API Keys → Create. The ea_live_ token is shown once — copy it into your secret manager.

  2. 2

    Make your first request

    Use the Authorization: Bearer header with the API key. JSON in, JSON out. Full reference at /documentation.

    curl -X POST https://emailalias.io/api/aliases \
  -H "Authorization: Bearer ea_live_…" \
  -H "Content-Type: application/json" \
  -d '{"alias_type":"random","label":"newsletter"}'
  3. 3

    Install the MCP server (optional)

    If you want AI-assistant management instead of raw HTTP, add the MCP server to your client's config. Three lines of JSON; works with every MCP-compatible client.

    {
  "mcpServers": {
    "emailalias": {
      "command": "npx",
      "args": ["-y", "@emailalias/mcp"],
      "env": { "EMAILALIAS_API_KEY": "ea_live_…" }
    }
  }
}

The full reference (auth, all endpoints, request/response shapes, cURL examples) lives at /documentation. The OpenAPI 3.1 spec is at /openapi.json.

What developers build with it

Patterns we see most often in customer integrations.

Per-tenant signup aliases (multi-tenant SaaS)

Mint a fresh alias for every customer signup so support inbound is auto-routed and per-tenant abuse is contained. One alias gets compromised? Disable it without touching anyone else's account.

Per-environment monitoring inboxes

alerts-prod@yourdomain → prod team, alerts-staging@yourdomain → staging on-call. Aliases on a custom domain give you clean environment routing without spinning up new mailboxes.

Test-account isolation

Generate disposable-style aliases for every signup in your test suite — accepted by real signup forms (unlike temp-mail), captured in your dashboard for assertions, and disabled when the test run ends.

Internal tooling + Slack bots

Wire the API into your admin dashboard or Slack bot so engineers can spin up aliases without leaving their tools. Each alias is rate-limited and tied to your team's billing.

Conversational management via MCP

Plug the MCP server into Claude Desktop or Cursor. "List the top 10 aliases by inbound volume" or "create a tagged alias for the new vendor signup" — without leaving your editor.

Frequently asked questions

The questions developers ask most often before they integrate.

Do you have an API?

Yes. We offer a RESTful API for programmatic alias management, exposure monitoring, and account management. Check our API documentation for endpoints, authentication, and usage examples.

Can I generate email aliases in bulk?

Yes, via the REST API on Premium. POST /api/aliases with alias_type and label generates one alias; loop it for as many as you need. Common bulk-generation use cases: marketplace listings (one alias per ad), security testing, A/B email-flow testing, and per-customer aliases on a custom domain. The MCP server lets AI assistants like Claude Desktop and Cursor call the same endpoint conversationally.

What does Premium include?

Unlimited aliases, up to 5 custom domains, unlimited verified forwarding inboxes (so each alias can route to the right mailbox), send & reply from any alias, real-time leak detection with exposure analytics, and priority processing — all for $4/month or $35/year (save 27%).

Can I move my aliases between providers?

Aliases on a shared provider domain (e.g. @emailalias.io) aren't portable — they live on our domain and stay with us. Aliases on a custom domain (yourdomain.com) are fully portable: you keep the domain, point its MX records at a new provider, re-create the same local-parts on their side, and the addresses keep working — provided the new provider supports custom local-parts (most do; some only issue random codes). Custom domains are a Premium feature on EmailAlias, but for anyone who plans to use aliases long-term, it's vendor-independence insurance worth having.

Can I use my own domain for email aliases?

Yes. Premium users can add up to 5 custom domains with full SPF, DKIM, and DMARC verification. Create professional aliases like contact@yourdomain.com while maintaining complete privacy.

Ship the integration

Get an API key and your first alias in five minutes. 7-day free trial on Premium — no credit card on the free tier.

Get an API keyRead the docs