Transactional Email API Service

Overview

Mailbase is a transactional email API service built around a workspace-scoped `/api/v1/send` endpoint. API tokens use scopes and expiry controls, requests can use idempotency keys, and provider message IDs are attributed per recipient for safer event matching.

Developer Controls

The developer API has an OpenAPI 3.1 contract, documented scopes, token expiry controls, and per-token plus workspace rate limiting with response headers.

Idempotency support protects send and create endpoints from duplicate retries, and `/api/v1/send` sends per recipient so provider message IDs can be mapped cleanly.

OpenAPI 3.1 contract
Scoped API tokens
Token expiry controls
Idempotency keys
Rate-limit headers

Email Workflow

Transactional sends still respect workspace sending state, suppressions, sender identity, reply handling, and analytics rollups. That keeps product email connected to the same operational context as campaigns.

Outgoing workspace webhooks can notify external systems about events with signed deliveries and delivery logs.

Workspace-scoped sending
Suppression enforcement
Per-recipient provider attribution
Analytics events
Signed outgoing webhooks

Common Mistakes

Choosing a tool before deciding who owns deliverability.
Treating DNS authentication as a one-time checkbox instead of an operating baseline.
Mixing product-critical transactional email with experimental marketing sends, with no clear boundary.
Trusting headline metrics (like open rate) that privacy proxies now inflate.