RESTful API, interactive Swagger docs, webhooks, and an MCP server for AI agents. Everything you need to integrate privacy-first email forwarding into your stack.
Two ways to integrate with RacterMX
Full OpenAPI 3.0 spec with interactive try-it-out. Manage domains, aliases, email logs, webhooks, blocklists, SMTP credentials, and more.
Open API Explorer →Model Context Protocol server for AI agents. Let Claude, GPT, or your own LLM manage email forwarding through natural language.
Learn more →Three supported authentication methods
Generate API keys from your dashboard. Pass them as a Bearer token in the Authorization header.
Authorization: Bearer sk_live_abc123...
For browser-based integrations. Authenticate via the web login and use session cookies with CSRF tokens.
Cookie: ractermx_session=abc123; X-CSRF-TOKEN: ...
The RacterMX API follows RESTful conventions. JSON in, JSON out. All endpoints live under /api/v2/ and require authentication.
https://ractermx.com/api/v2# Send an email via the RacterMX API curl -X POST https://ractermx.com/api/v2/emails/send \ -H "Authorization: Bearer sk_live_abc123" \ -H "Content-Type: application/json" \ -d '{ "from": "hello@yourdomain.com", "to": ["user@example.com"], "subject": "Hello from RacterMX", "html": "<h1>It works!</h1>" }' # Response { "success": true, "message_id": "<abc123@yourdomain.com>" }
All endpoints require authentication. Base URL: https://ractermx.com/api/v2
Let AI manage your email forwarding through natural language
The RacterMX MCP server exposes every API endpoint as a tool that AI agents can call. Connect it to Claude, ChatGPT, or any MCP-compatible client to manage domains, aliases, and email forwarding conversationally.
// Add to your MCP client config { "mcpServers": { "ractermx": { "command": "npx", "args": ["@ractermx/mcp-server"], "env": { "RACTERMX_API_KEY": "sk_live_abc123" } } } } // Then ask your AI agent: "List all my domains on RacterMX" "Create an alias catch-all@mydomain.com" "Show me email logs from the last hour"