mailbridgeAPI
Log 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.

Start your free trialExplore the docs

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.

ONE MAILBOX. CLEAR ENDPOINTS.

Turn a standard email mailbox into an API.

Connect SMTP and IMAP once. MailBridgeAPI gives your applications HTTP endpoints to trigger actions with that mailbox, while you keep your existing address and provider.

your@email.comSMTP + IMAP
MailBridgeAPI
Available endpointPOST /sendemail/

Send email

Trigger an API request to send from your connected address.

Available endpointGET /getemail/

Retrieve email

Read messages from the connected mailbox through a JSON response.

Available endpointGET /email/unsubscribed/

Sync unsubscribes

Retrieve opt-out records for your own contact workflows.

See every parameter
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 response = await fetch(
  'https://api.mailbridgeapi.com/sendemail/',
  {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      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 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
01
DEVELOPMENT TEAMS

Connect one mailbox to several projects.

Use the same mailbox across internal tools and applications while managing its connection settings centrally.

02
AGENCIES & FREELANCERS

Build for clients without asking for their email password.

Connect a client’s mailbox to their website or application using API keys. The client handles the mailbox credentials.

03
CUSTOMER SUPPORT

Put email conversations where your team works.

Read customer messages inside your support tool and send replies from your existing support address.

04
FINANCE & OPERATIONS

Send invoices from the address customers recognize.

Deliver invoices, payment instructions, and follow-ups from your accounting workflow.

05
E-COMMERCE & BOOKINGS

Keep customers informed as an order moves forward.

Send order updates, appointment details, and booking confirmations from your own business mailbox.

06
AI-ASSISTED WORK

Turn incoming emails into useful input for your AI tools.

Build email classification, request summaries, and reply drafts around a connected mailbox.

SIMPLE BY DESIGN.

Small price. Full possibility.

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

See pricing
MailBridgeAPI

Your complete email-to-API toolkit.

$9/ monthUSD

Billed monthly. $9 USD per month.

Start your free trial
3-day free trial · No credit card required

Included in both plans

  • Full access to MailBridgeAPI
  • Unlimited email API requests
  • SMTP sending and IMAP retrieval
  • Dashboard and API key management
  • Headers, footers, and unsubscribe tools
  • Priority support

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

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?

Both published plans include 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.

Start your free trialRead the documentation
3-day free trial·No credit card required