mailbridgeAPI
Log inConnect a mailbox
CONTINUOUS MAILBOX OVERSIGHT

Know when email delivery starts to slip.

A mailbox can work today and lose deliverability tomorrow. Schedule recurring checks in your dashboard to spot SMTP, security, authentication or reputation changes before they disrupt important outgoing email.

From every 60 minutesAlerts on your chosen score thresholdEmail report and optional mobile push
INCLUDED WITH YOUR PAID PLAN

Included in paid plans from per month

Recurring deliverability monitoring is included with an active paid subscription. No separate monitoring add-on is required.

Compare plans
SMALL CHANGES CAN HAVE A BIG IMPACT

Email delivery is part of your operations.

SMTP settings, TLS certificates, domain authentication and sender reputation can change over time. A configuration update or a new spam signal may lower a mailbox score without an obvious warning in your application.

SMTP or security changes

A password rotation, port change, expired certificate or TLS issue can interrupt the sending path.

Domain authentication drift

Changes to SPF, DKIM or DMARC records can affect how receiving providers evaluate your messages.

Reputation and spam signals

Blocklist listings or other reputation signals may appear after a mailbox was configured and tested.

ILLUSTRATIVE MONTHLY SCENARIO

A campaign that lands in spam can put thousands at risk.

A sending system may accept a message even when a promotion later lands in spam. The sender can see a successful handoff while customers never notice the offer.

Campaign volume4,000

4 weekly sends × 1,000 recipients each

Assumed orders80

80 orders at an illustrative 2% purchase rate

Average order value

Assumed average value per order

Potential gross sales at risk

If all four campaigns go unseen

80 assumed orders × average order value = gross sales opportunity.

Illustration only, not a forecast, confirmed loss or promise. This is gross revenue before costs. Real inbox placement, conversions and sales vary. Monitoring can surface technical or reputation warnings, but cannot guarantee inbox placement or sales.

MONITOR FROM THE DASHBOARD

A recurring check with a clear next step.

Choose how often MailBridgeAPI should check the connected mailbox, define the conditions that matter to your team, and keep a history of recurring reports beside your other deliverability checks.

01

Choose a schedule

Build a schedule in the dashboard. The shortest interval is 60 minutes, with options to choose the time and calendar cadence.

02

Set your alert threshold

Choose the minimum score that is acceptable for this mailbox. You can also be alerted when a report fails or stays pending for more than five minutes.

03

Review every result

Recurring reports are kept in the deliverability history and identified as automatic, so your team can follow changes over time.

GET THE SIGNAL WHERE YOU NEED IT

An alert should reach the person who can act.

Choose email alerts, mobile push notifications, or both. Email alerts go to your account email by default; you can enter another recipient. The alert includes the reason, mailbox and score, plus report details and a link to the full result.

Email alerts

Send an actionable report to the account address or a recipient you choose.

Mobile push alerts

Get a notification on your phone when the MailBridgeAPI app is installed, signed in and allowed to send notifications.

GET THE SIGNAL WHERE YOU NEED IT
  • The score falls below your chosen minimum
  • A diagnostic fails
  • A report is still pending after five minutes, if you enable that condition

Alerts are sent when a monitored issue is detected; recovery is recorded by later checks. A score is a diagnostic signal, not a guarantee that every provider will place a message in the inbox.

A REPORT, NOT JUST A WARNING

See what failed and what to do next.

The alert email puts the result in context: a color-coded overall status, the mailbox and score, then diagnostic checks ordered by priority. Each check explains the finding and, when available, gives a recommended action. The full report remains one click away.

Failures and warnings appear before successful checks, so the items that need attention are easy to find.
Illustrative reportFailure
EMAIL SUBJECTMailBridgeAPI alert: mailbox deliverability needs attention
orders@example.comDELIVERABILITY SCORE
5.8 / 10
FailureMain issue

SPF record needs attention

Recommended action

Review the SPF record for this sending domain.

Failure
SPF authentication

The sending domain has a record that needs correction.

Warning
Sender reputation

A reputation signal deserves a closer look.

Success
SMTP connection

The mailbox accepted the diagnostic message.

See the full report format
WHERE CONTINUOUS CHECKS HELP

Protect the mailbox behind important workflows.

01

Online stores

Watch the mailbox used for order confirmations, receipts and customer updates.

02

Customer support teams

Catch delivery problems affecting replies, case updates and service notifications.

03

Agencies and multi-site teams

Keep an eye on client mailboxes after credential rotations, DNS changes or provider updates.

04

SaaS and business applications

Monitor the sender used for account notices, security messages and workflow alerts.

THREE STEPS TO ACTIVE MONITORING

Configure it once. Let the schedule do the checking.

01

Connect a mailbox

Add the SMTP settings for the mailbox you want to monitor in the MailBridgeAPI dashboard.

02

Choose schedule and alerts

Set the cadence, score threshold, alert channels and recipient for that mailbox.

03

Follow the report history

Review automatic checks, investigate changes and use the recommended actions to correct issues.

An active paid subscription includes up to 100 completed deliverability checks per account per UTC day. Recurring checks use this allowance; additional completed checks use global Credits.

KEEP YOUR OUTBOUND EMAIL VISIBLE

Find a deliverability change before it becomes a customer issue.

Set up a recurring check for a connected mailbox, then let the dashboard and alerts keep your team informed.

YOUR OWN MAILBOX. YOUR API KEYS. YOUR REQUESTS.

Connect your own mailbox to API keys, then control it through endpoints.

MailBridgeAPI links the SMTP and IMAP mailbox you own or are authorized to use to an account API key and a mailbox API key. Every request selects that same mailbox: send from its address, read its received messages, or process them in your applications.

Explore the docs
Your own mailboxapikey + apikeyboxAPI endpoint requestAction through that mailbox
POST /sendemail/

Send through your mailbox

A POST request uses the SMTP connection of the mailbox selected by apikeybox and sends from that mailbox.

GET /getemail/

Read your mailbox

A GET request uses the same mailbox key to retrieve messages from its configured IMAP folders.

YOUR LOGIC. YOUR WORKFLOW.

Use your mailbox data

Your authorized application handles the result in its workflows, automations, CRM, support tools, or AI systems.

Connect only a mailbox you own or are authorized to use. The provider must allow compatible SMTP or IMAP access, and its limits still apply.