Give every caller only the authority it needs.
Marmunk supports tenant-bound API keys, browser sessions, and delegated OAuth for MCP. Sending approval remains a separate control.
API keys
Use Bearer authentication for server-to-server API calls. Keys are shown once, strongly hashed at rest, tenant-bound, expiring, and revocable.
Authorization: Bearer mmk_key_...Never put a Marmunk key in browser code. Keep it in your server-side secret store and redact it from logs and support artifacts.
Core scopes
email.sendSubmit approved email intents.email.readRead messages, delivery events, and safe traces.webhook.manageCreate endpoints and rotate signing secrets.suppression.manageManage customer-controlled recipient blocks.usage.readRead current limits and reserved usage.Agent access
OAuth-capable MCP clients should connect to https://api.marmunk.com/mcp. Browserless runtimes use a separately created, expiring agent credential with an explicit scope set.
Agent credentials cannot create accounts, accept legal terms, mint API keys, submit sending applications, or call operator routes.