Mailbase Developer Docs

Production integration notes for teams that want Mailbase to sit cleanly inside their app, backend jobs, AI tools, and self-hosted email stack.

Start Here

Mailbase has two integration surfaces: the REST API for product teams that need deterministic backend calls, and the MCP server for AI-assisted workflow clients. Both are workspace-scoped and designed around your sender domains, audiences, campaigns, replies, managed sending, and optional BYO useSend setup.

If you’re wiring Mailbase into a live product, start with the REST API reference for authentication, scoped tokens, transactional send, campaigns, and audiences — every endpoint is scoped to a single workspace so multi-tenant data never crosses boundaries. Teams building AI-assisted email workflows can instead connect the MCP server to clients like Claude Code, Cursor, or Codex, where drafts always land for human review before anything sends.

REST API

Send transactional email, list campaigns, and create audiences from your backend.

Open docs Operations

Cron setup

Configure the recurring Mailbase cron endpoints that enqueue scheduled campaigns, process durable send-job batches, and run due workflow steps.

Open docs Compliance

Unsubscribe compliance

How Mailbase signs unsubscribe links, enforces suppression states, adds List-Unsubscribe headers, and keeps marketing sends compliant.

Open docs Developer API

API tokens

Create, scope, rotate, and verify Mailbase API tokens for workspace-safe backend integrations.

Open docs Deliverability

Sender domains

Connect sender domains, understand hosted versus BYO useSend sending, and keep SPF, DKIM, and DMARC status visible in Mailbase.

Open docs MCP

MCP OAuth

Connect Claude, Cursor, Codex, or another MCP client to Mailbase with OAuth-scoped workspace access.

Open docs Integrations

No-code integrations

Connect Mailbase to Zapier, Make, or n8n with REST Hooks: subscribe a callback URL to an event, sample real payloads while you build, and unsubscribe when the automation is turned off.

Open docs

useSend integration

Configure managed sending or connect your own useSend instance, API key, webhooks, sender domains, and reply inbox.

Open docs

Pricing model

Understand transactional volume, marketing contacts, and bring-your-own useSend.

Open docs

Professional Integration Checklist

Create a workspace and verify at least one sender domain.
Open Settings, then Developer API, and create a scoped API token.
Store the token in your backend secret manager, never in frontend code.
Call /api/v1/me from CI or staging to verify the token scope.
Use /api/v1/send for transactional email from your app.
Use useSend webhooks so delivery, bounce, complaint, and reply events flow back.