Workspaces & roles
A workspace (organization) owns domains, API keys, messages, and credit accounts. Membership roles gate mutations: Owners manage billing and deletion, Admins operate infrastructure, Members send, Viewers read.
Documentation
These guides mirror the product invariants. API references expand as each vertical slice lands.
Organizations, membership, and Owner / Admin / Member / Viewer permissions.
Add a domain, publish SPF/DKIM/DMARC, and move through verification states.
Create a Bearer key, send with POST /api/emails, and revoke keys you no longer use.
HTTP enqueues the send. Workers deliver it and post signed events to your endpoints.
Included credits, packs, ledger semantics, and subscription intervals.
Health endpoints, queue workers, and what the admin command center monitors.
A workspace (organization) owns domains, API keys, messages, and credit accounts. Membership roles gate mutations: Owners manage billing and deletion, Admins operate infrastructure, Members send, Viewers read.
Adding a domain creates pending DNS instructions. Background verification jobs check SPF, DKIM, and DMARC. Only verified domains become eligible for active sending.
# Example SPF (illustrative) v=spf1 include:amazonses.com ~all
Create a key in the dashboard and send with Authorization: Bearer. The secret is shown once. Revoked keys stop authenticating immediately.
POST /api/emails checks the API key, the verified from-domain, and the suppression list, then enqueues a durable job. Workers call the provider. Customer webhooks receive sent, delivered, bounced, and failed events.
Plans and credit packs live in Postgres. Subscriptions reference plan rows; credit accounts update through an immutable ledger. Marketing pricing reads the same tables your billing UI will.
GET /api/health reports database and queue readiness. Workers consume BullMQ queues for domain verification, sends, and webhook delivery. The admin command center observes jobs without bypassing tenant authz for customer data mutations.