mailbridgeAPI
DEMOLog inStart building
YOUR MAILBOX. NOW PROGRAMMABLE.

Your email.
Your workflow.
One simple API.

Turn a standard SMTP and IMAP mailbox into an email API. Your applications can call clear HTTP endpoints to send, receive, and automate email from your own address—without sharing the mailbox password with your developer.

No account needed: verify SMTP or IMAP, receive temporary API keys, and copy ready-to-run integration code in minutes.

3-day free trial·No credit card required

FROM YOUR INBOX TO YOUR APPLICATION
Your existing mailboxhello@yourcompany.com
Connected
SMTPIMAP
Secure connection
MailBridgeAPIAPI key
your-next-big-idea.jsPOST /sendemail/
await fetch(MAILBRIDGE_URL, {
  method: 'POST',
  body: new URLSearchParams({
    apikey: process.env.MAILBRIDGE_API_KEY,
    apikeybox: process.env.MAILBRIDGE_BOX_KEY
  })
});
Your mailbox. Connected to your code.{ sent: "OK" }
Less configuration.More creation.

SEE THE CONNECTION

One mailbox becomes an API your projects can use.

MailBridgeAPI securely links your SMTP and IMAP mailbox to two API keys. Your applications then call clear endpoints to send email and process received messages without using the mailbox password.

01Your mailboxyou@company.comYour address and provider
02MailBridgeAPI
Mailbox API keymbox_••••7F3A
Linked and ready
03Callable endpoints
POST /sendemail/
GET /getemail/
GET /email/unsubscribed/
04Your projects
WebsiteCRMAutomation
Your project keeps the API keys on its server. The mailbox password stays in the MailBridgeAPI configuration.
See every parameter

EMAIL IS BUSINESS-CRITICAL.

Integrate your mailbox—and know it is working.

MailBridgeAPI serves two needs at once: developers get a consistent email API for their projects, while companies get a fast way to check the mailboxes their activity depends on.

FOR DEVELOPERS

Build without rebuilding SMTP and IMAP

Use stable HTTP endpoints for sending, receiving, searching and health data in every authorized integration.

FOR COMPANIES

Keep critical mailboxes under control

Check access, test outgoing and incoming connections, and find sending errors before they disrupt customers or operations.

Explore every control endpoint
MAILBOX CONTROL

The essentials, visible in one place.

Use the dashboard, mobile application or API endpoints to verify the service quickly.

Mailbox accessible

Confirm that the configured account can still be reached.

CHECK ACCESS

SMTP operational

Test the outgoing connection used by your applications.

TEST SMTP

IMAP operational

Test access to incoming messages and folders.

TEST IMAP

Sending errors visible

Open the activity log, identify the reason and act quickly.

VIEW ERRORS

Email carries customer requests, confirmations, invoices and alerts. Its availability should never be left to guesswork.

YOUR PROVIDER. YOUR ADDRESS. YOUR RULES.
Google WorkspaceMicrosoft 365Zoho MailOVHcloud SMTP / IMAP

Requires compatible SMTP and IMAP access. Your provider may require an app password or specific account settings.

A SMALL BRIDGE. A BIG DIFFERENCE.

Email integration, without the heavy lifting.

Your mailbox already works. MailBridgeAPI turns it into callable endpoints that any HTTP-capable application can use.

Send from your own address · Bring your inbox into your app
POST /sendemail/GET /getemail/

Send from your own address

Send transactional emails and notifications through your connected SMTP mailbox. Your provider and sender identity stay with you.

Explore feature

Bring your inbox into your app

Retrieve incoming messages from your IMAP folders. Turn customer requests, alerts, and replies into useful application data.

Explore feature

Integrate without the mailbox password

The mailbox owner enters their credentials in MailBridgeAPI. Your developer uses API keys to connect the project, without needing to know the email password.

Explore feature
THREE STEPS. ENDLESS POSSIBILITIES.

From inbox to integration.

A familiar mailbox on one side. Your next great idea on the other.

01

Connect your mailbox

Add your SMTP and IMAP settings in the dashboard. Keep using your existing address and email provider.

SMTP + IMAP
02

Get your API keys

Use your account API key and the key for your chosen mailbox. Your application never needs the mailbox password.

API KEY + MAILBOX KEY
03

Make your first request

Send a message, retrieve your inbox, or connect email to the tools and workflows you already use.

HTTP REQUEST → EMAIL
ONE MAILBOX. EVERY PROJECT.

Change the mailbox password once. Keep every project running.

Imagine that the same SMTP mailbox sends email from a website, an invoicing tool, internal automations and dozens more projects. When its password or provider settings change, update the connection once in MailBridgeAPI.

Without MailBridgeAPI

Every project stores the SMTP configuration. A password change becomes a search through every application, followed by new deployments and the risk of forgetting one.

WebsiteSMTP ••••••••01
Billing appSMTP ••••••••02
AutomationSMTP ••••••••03

With MailBridgeAPI

Every project calls the same email API. Update the mailbox connection in the dashboard; the applications keep using their existing API integration.

Mailbox settingsUpdate SMTP / IMAP once
Website
Billing app
Automation
One change instead of one change per project.

Whether the mailbox is used by three projects or hundreds, no source-code or deployment change is needed when only its mailbox password or connection settings change.

YOUR PROJECT NEEDS EMAIL. NOT THE EMAIL PASSWORD.

Integrate the mailbox. Keep its password out of the project.

Your client or mailbox owner connects the email account in MailBridgeAPI. You build the integration with API keys, without needing to know their mailbox password.

See the client integration example
Integrate the mailbox. Keep its password out of the project.
Mailbox owner

Enters SMTP / IMAP credentials in MailBridgeAPI.

MAILBOX CREDENTIALS
MailBridgeAPI

Uses the configured connection to communicate with the mailbox.

API KEYS
Developer & application

Uses account and mailbox API keys to send or retrieve emails.

The developer does not need the mailbox password.

A more reassuring client handoff

The owner enters the mailbox credentials. The developer receives the API access needed for the integration.

Fewer places to share a password

Keep the mailbox password out of project source code, developer messages, and individual application configurations.

One place for connection settings

When mailbox settings change, update the connection in the dashboard instead of redistributing the password across projects.

MailBridgeAPI still needs the owner’s mailbox credentials to connect to the email provider. API keys grant access to email operations: treat them as secrets and keep them in your backend.

MADE FOR THE WAY YOU BUILD.

A few lines of code. A lot of possibility.

Straightforward HTTP requests. Familiar JSON responses. Bring email into your stack without writing another SMTP or IMAP integration.

  • Send text, HTML, and attachments
  • Read messages from your IMAP folders
  • Use JavaScript, Python, PHP, or any HTTP client
Read the documentation
const form = new URLSearchParams({
  apikey: process.env.MAILBRIDGE_API_KEY,
  apikeybox: process.env.MAILBRIDGE_BOX_KEY,
  recipient_email: 'jane@example.com',
  mail_subject: 'Hello, possibilities.',
  mail_body: 'Your next idea starts here.',
  format: 'text'
});
const response = await fetch(
  'https://api.mailbridgeapi.com/sendemail/',
  { method: 'POST', body: form }
);
const data = await response.json();
// Check data.result.error, not just HTTP status.
console.log(data);
Example only — no live requests
ONE MAILBOX. MANY WAYS TO BUILD.

Real work. Real reasons to connect.

For the person writing the code, the team using the tool, and the client who owns the mailbox.

Explore all use cases
SIMPLE BY DESIGN.

Small price. Full possibility.

One complete feature set. Choose the billing cycle that works for you.

See pricing

Up to

2connected mailboxes

Starter

/ month

  • Full access to MailBridgeAPI
  • Unlimited email API requests
  • SMTP sending and IMAP retrieval
  • Dashboard and API key management
Choose this plan

Up to

10connected mailboxes

Business

/ month

  • Full access to MailBridgeAPI
  • Unlimited email API requests
  • SMTP sending and IMAP retrieval
  • Dashboard and API key management
Choose this plan

Up to

25connected mailboxes

Scale

/ month

  • Full access to MailBridgeAPI
  • Unlimited email API requests
  • SMTP sending and IMAP retrieval
  • Dashboard and API key management
Choose this plan

More than 25 mailboxes

Unlimited

Managing a larger email fleet? Contact us for an unlimited plan adapted to your monitoring and support needs.

CustomContact support

Endpoint rate limits and your email provider’s sending policies apply.

3-day free trial · No credit card required
FAQ

A few things you might be wondering.

Talk to us
Do I need to change my email provider?

No. MailBridgeAPI connects to an existing mailbox using SMTP for sending and IMAP for reading. Your provider must allow compatible access, and may require an app password or particular security settings.

What do I need to get started?

An account and the connection settings for a mailbox you are authorized to use: SMTP and IMAP hosts, ports, usernames, and credentials. Add these in the dashboard, then use your account API key and mailbox key in your requests.

Can I connect more than one mailbox?

Yes. You can configure multiple mailboxes and choose the one to use with the apikeybox parameter. Check your account or contact us for any mailbox limits applicable to your subscription.

Can a developer integrate my mailbox without knowing its password?

Yes. You enter the mailbox’s SMTP and IMAP credentials yourself in the MailBridgeAPI dashboard. Your authorized developer uses your account API key and mailbox key in the project’s backend. They do not need your mailbox password. MailBridgeAPI needs those credentials to connect to your provider, and the API keys must also be kept secret because they allow email operations.

Can I use MailBridgeAPI with my own business tools or AI workflows?

Yes. Any backend or automation tool that can make HTTP requests can use the documented endpoints. Your application supplies the workflow logic, scheduling, customer matching, and any AI processing. These are integrations you build, rather than preconfigured applications included with the API.

Are email API requests unlimited?

Every paid tier includes unlimited email API requests. Individual endpoints have rate limits, and your email provider’s sending limits and acceptable-use rules still apply.

How does the free trial work?

You can try MailBridgeAPI for 3 days without a credit card. Choose monthly or annual billing when you are ready to continue.

YOUR NEXT INTEGRATION STARTS HERE.

Build more with the inbox you already have.

Turn your mailbox into an API, call your first email endpoint, and give every project a simpler way to send or retrieve messages.

3-day free trial·No credit card required
ANY SMTP/IMAP MAILBOX. ONE POWERFUL API.

Turn the mailbox you already use into an API your entire stack can call.

Connect a compatible mailbox once. MailBridgeAPI exposes clear endpoints so your applications can send through SMTP, retrieve incoming messages through IMAP, and process those emails in your own workflows, automations, CRM, support tools, or AI systems.

Explore the docs
POST /sendemail/

Send by API

Trigger transactional emails, alerts, documents, and replies from your existing address.

GET /getemail/

Retrieve received email

Read incoming messages and mailbox folders through structured JSON responses.

YOUR LOGIC. YOUR WORKFLOW.

Power your own workflow

Classify, route, store, summarize, or respond using the business logic and tools you choose.

Works with email providers that allow compatible SMTP and IMAP access. Provider limits still apply.