Connect Mission Inbox OBM API to SuperSend
Connect Mission Inbox OBM API to SuperSend
Purpose
The Mission Inbox OBM (Outbound Mail) API enables high-volume sending through Mission Inbox's managed infrastructure. This article walks through connecting your Mission Inbox API to SuperSend, syncing domains, creating send-as mailboxes, and configuring reply routing so you can run campaigns at scale with full Super Inbox support.
Prerequisites
- A Mission Inbox account with at least one domain configured
- Your Mission Inbox API key (from Mission Inbox → Settings → Platform API)
- Org admin permissions in SuperSend
Step 1: Get Your Mission Inbox API Key
- Log in to Mission Inbox
- Go to Settings → Platform API
- Find your API key and copy it
Step 2: Connect Mission Inbox in SuperSend
- Log in to SuperSend
- Go to Admin → Integrations
- Select your team from the dropdown
- In the Sending Providers section, find MissionInbox
- Click Manage → Add Account
- Paste your API key and save
Domains sync automatically — Within about 5 minutes, all domains from your Mission Inbox account will appear in SuperSend. You can then create send-as mailboxes on those domains.
Step 3: Add OBM API Senders
You can add senders in two ways: single sender or bulk import via CSV.
Option A: Add a Single Sender
- Go to Senders → Add Sender → Email Sender
- Click Connect Your Own Mailboxes
- Find Mission Inbox OBM API under "Email API Providers" and click it
- Enter:
- API Key — your Mission Inbox API key (or use the one from Admin → Integrations if connected)
- Send As Email — an email address using a domain synced from your Mission Inbox account (e.g.
curtis@meet.teamsupersend.com) - Reply-To Email — where replies should be directed (for Super Send reply routing, use an address that routes to SuperSend)
- Track Replies — enable if your Mission Inbox plan supports reply detection
- Click Connect
Option B: Bulk Import via CSV
- Go to Senders → Add Sender → Email Sender
- Click Connect Your Own Mailboxes
- Select Mission Inbox OBM API (or Mission Inbox bulk import option if available)
- Click Bulk import via CSV
- Download the CSV template and fill in:
email— email address (must use a synced domain)send_as— display namereply_to— reply-to address for Super Send reply routingglobal_max_per_day— daily send limit (e.g. 25)
- Upload the completed CSV
Typical setup for ~500 cold emails/day: Configure about 16–17 senders with a global max of ~25 emails per day each. Mission Inbox allows up to 500 cold production emails per day; this spread keeps you within that limit.
Step 4: Reply Routing
OBM API senders support two reply routing options:
Super Send Reply Routing (recommended)
- When prospects reply, emails come to SuperSend
- Replies appear in Super Inbox
- Enables auto-pause contacts, unsubscribe handling, reply detection
- Requires one MX record on your sending domain (see Step 5)
External Reply Routing
- Replies do not come to SuperSend
- No Super Inbox, no auto-pause or reply-based features
- Simpler setup, but limited functionality
Step 5: DNS Record for Super Send Reply Routing
If you use Super Send reply routing, add this MX record on the root domain of each sending domain.
Example: For meet.teamsupersend.com, the root domain is teamsupersend.com.
Field | Value |
|---|---|
Host | |
Value | |
Priority | |
DNS changes may take up to 24–48 hours to propagate.
Step 6: Attach to a Sender Profile
After adding OBM senders, attach them to a sender profile so campaigns can use them:
- Go to Senders → Sender Profiles tab
- Open a profile (or create one)
- Click Add Mailboxes and select the Mission Inbox OBM senders
- Save
See Create and Use Sender Profiles for details.
Step 7: Ramp Up (Recommended)
Mission Inbox recommends ramping up new infrastructure gradually. On each sender, configure ramp-up in the Limits tab:
- Example: If your target is 25 emails per day, set a ramp-up of 5 emails over 14 days
- SuperSend will start at 5/day and increase over 14 days until you reach 25/day
Expected Result
Mission Inbox OBM API senders are connected, domains are synced, send-as mailboxes are created, and reply routing is configured. Senders appear in Senders → Mailboxes and can be attached to sender profiles for campaign use.
Troubleshooting
- Issue: Domains don't sync after adding the integration.
Fix: Verify the API key is correct. Allow 5 minutes for sync, then refresh. Check that your Mission Inbox account has domains configured.
- Issue: OBM API sender connected but emails aren't going out.
Fix: Verify the sending domain is verified and active in your Mission Inbox account. Confirm the sender profile is assigned to the campaign. Check that you're within Mission Inbox daily limits.
- Issue: Replies aren't appearing in Super Inbox.
Fix: Confirm you're using Super Send reply routing and that the MX record (replies → supersendtech.com) is correctly set on the root domain.
Related Articles
Updated on: 17/03/2026
Thank you!