mailbridgeAPI
DEMOLog inConnect a mailbox
ONE MAILBOX. MANY WAYS TO BUILD.

Email API use cases for your business.

Connect your own mailbox to account and mailbox API keys, then let websites, support tools and automations send requests that act through that same mailbox.

Email API use cases for your business.

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.

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.

One connection. Value at every level.

01

For mailbox owners

Keep your familiar address and enter your connection settings yourself. A developer can integrate your mailbox without asking for its password.

02

For developers and agencies

Use account and mailbox API keys in your backend. Reuse the same HTTP integration pattern across client projects.

03

For business teams

Bring emails into the tools you already work in, and send updates from the address your customers recognize.

01DEVELOPMENT TEAMS

Connect one mailbox to several projects.

Imagine this

A website, an invoicing tool, and an operations script all use the same mailbox. A provider setting changes.

What your team gains

Mailbox configuration lives in one place. You avoid distributing the mailbox password across each project.

How you build it

  1. Configure the mailbox’s SMTP and IMAP access in MailBridgeAPI.
  2. Your authorized projects use the account and mailbox keys for their requests.
  3. Update the mailbox connection in the dashboard when its provider settings change.
Explore the endpoint
02AGENCIES & FREELANCERS

Build for clients without asking for their email password.

Imagine this

A client wants their website to send enquiry acknowledgements from contact@theircompany.com, but does not want to share the mailbox password with the development team.

What your team gains

A clearer handoff: the client manages the mailbox connection, while the developer works with API access.

How you build it

  1. The client enters their SMTP and IMAP settings in the MailBridgeAPI dashboard.
  2. They provide the account API key and the key for the mailbox to the authorized developer.
  3. The developer keeps those keys in the project’s server configuration and sends acknowledgements through the API.
Explore the endpoint
03CUSTOMER SUPPORT

Put email conversations where your team works.

Imagine this

Your team switches between a shared inbox and an internal support application to handle the same customer requests.

What your team gains

Less switching between tools and a customer conversation attached to the work it belongs to.

How you build it

  1. Your application fetches messages from the support mailbox’s INBOX.
  2. It associates messages with customer records or tickets using your own matching rules.
  3. An agent writes a response in your tool; your backend sends it through the connected mailbox.
Explore the endpoint
04FINANCE & OPERATIONS

Send invoices from the address customers recognize.

Imagine this

An invoice is ready in your internal system. Someone still downloads the PDF, opens an email client, and attaches it by hand.

What your team gains

Fewer manual steps, consistent email content, and a recognizable sender for your customers.

How you build it

  1. Your application generates the invoice and prepares the recipient and message.
  2. It encodes the PDF attachment and calls the sending endpoint.
  3. It checks the API’s SMTP result and records that result against the invoice.
Explore the endpoint
05E-COMMERCE & BOOKINGS

Keep customers informed as an order moves forward.

Imagine this

A booking is confirmed or an order changes status in your application. The customer needs the right details at the right moment.

What your team gains

Communication follows the business event, using the email identity your customer already knows.

How you build it

  1. Your application detects the order or booking event.
  2. It prepares an email using the customer’s details and the event information.
  3. Your backend sends the message through MailBridgeAPI and checks the send result.
Explore the endpoint
06AI-ASSISTED WORK

Turn incoming emails into useful input for your AI tools.

Imagine this

Your team receives repetitive enquiries and wants help identifying the topic and preparing a first draft.

What your team gains

A practical route from inbox content to assisted work, with human review where you need it.

How you build it

  1. Your backend retrieves the relevant messages through the IMAP endpoint.
  2. Your chosen AI service summarizes or classifies the content according to your rules.
  3. Your team reviews a draft before your application sends the approved response.
Explore the endpoint
07AUTOMATION & INTERNAL TOOLS

Make email a step in your existing workflow.

Imagine this

An approved request in your business system should trigger an email, or a scheduled workflow needs to collect new inbox messages.

What your team gains

Email becomes part of the process instead of a separate task someone has to remember.

How you build it

  1. Configure a scheduled job or an event in your application or automation tool.
  2. Use its HTTP request step with your account and mailbox keys.
  3. Process the JSON response and decide what the next step should do.
Explore the endpoint
08CUSTOMER COMMUNICATION

Keep opt-out records connected to your contact list.

Imagine this

Your application sends customer communications and needs to respect recipients who have asked to opt out.

What your team gains

Opt-out information becomes part of your list-management workflow, instead of a disconnected record.

How you build it

  1. Configure the unsubscribe footer and enable it on the relevant sends.
  2. Retrieve unsubscribe records for the mailbox through the API.
  3. Match those recipients to your contact list and exclude them from future applicable mailings.
Explore the endpoint

Each workflow uses account and mailbox API keys to select and operate your connected mailbox. Your application provides the business logic, scheduling, and any AI processing. Provider access and sending limits still apply.

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.

YOUR NEXT INTEGRATION STARTS HERE.

Build more with the inbox you already have.

Connect your own mailbox to its API keys, call your first endpoint, and let every authorized project send from or retrieve messages from that same mailbox.

Start your free trialRead the documentation
3-day free trial·No credit card required
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.