For developers
One API for newsletters and every other email.
Order confirmations from your shop, posts from your CMS, signups from your app: all through the same verified domain as your newsletter.
POST /api/v1/{slug}/send API-KEY: •••••• API-SECRET: •••••• { "from": "[email protected]", "to": "[email protected]", "subject": "Your order #10023", "html": "<p>Thank you for your order.</p>" }
POST /api/v1/{slug}/posts API-KEY: •••••• API-SECRET: •••••• { "subject": "Our November update", "html": "<p>Hello, here is what is new …</p>", "send_at": "2026-11-14T07:30:00+01:00" }
POST /api/v1/{slug}/add-subscriber API-KEY: •••••• API-SECRET: •••••• { "email": "[email protected]", "segments": ["Buyer", "Hamburg"] }
What you can build
POST /sendTransactional emailsPassword links and order confirmations, with bounce and complaint suppression.
SMTPSMTP relayFor systems that only speak SMTP. Same delivery, same suppression list.
POST /postsPostsCreate issues from your CMS: as a draft, right away or scheduled.
POST /add-subscriberSubscribersSubscribe with double opt-in, unsubscribe, report bounces of your own mail server.
MCP server
Your AI assistant writes the draft
Connect Claude, ChatGPT or Cursor to Obanox. You sign in with your Obanox login, not an API key, and you can disconnect any app at any time.
create_newsletter_draftcreates a draft for you to review and sendsend_emailsends a single email from your domain
One key for everything
Several named keys per account, each for all newsletters and APIs. Revoke them one by one.
Clear errors
JSON with a status code and a message. Only 429 succeeds later; do not repeat other 4xx errors unchanged.
Which plans
The API, the SMTP relay and the MCP server are part of these plans: Pro, Business. Pricing