mailbridgeAPI
DEMOLog inStart building
BUILT AROUND YOUR MAILBOX.

Email API features for your daily workflows.

Everything your applications need to act on your own connected mailbox through API requests: sending, reading, monitoring, mailbox access, and consistent communication.

Email API features for your daily workflows.

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.

A COMPLETE AI RESPONSE WORKFLOW

Turn received email into useful, controlled action.

Understand the request, enrich the draft with authorized data, keep the conversation thread and decide whether AI sends or a person approves.

  • Automatic or approval-based delivery
  • External API integrations
  • Mobile review and full history
Discover AI connected to email

Send from your own address

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

  • HTML or plain text messages
  • Custom sender and reply-to names
  • CC recipients and base64 attachments
POST /sendemail/

Bring your inbox into your app

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

  • Select an IMAP folder
  • Retrieve up to 30 messages per page
  • Work with a JSON response
GET /getemail

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.

  • The owner configures the mailbox connection
  • Your backend uses account and mailbox keys
  • Mailbox passwords stay out of project code
apikey + apikeybox

Consistent emails, by default

Configure a shared header and footer in the dashboard. Keep your branding and signature consistent across the emails your applications send.

  • Reusable headers and footers
  • Company signatures and disclaimers
  • Update content from your dashboard
CONFIGURE ONCE

Keep your contact lists in sync

Enable unsubscribe links for your mailings and retrieve opt-out records through the API to update your own contact lists.

  • Optional unsubscribe footer
  • Recipient-specific opt-out links
  • Retrieve unsubscribe records by mailbox
GET /email/unsubscribed/

Make email part of your workflow

Connect API requests to your business logic. Build automated responses, data extraction, or AI-assisted workflows around your existing mailbox.

  • Integrate from any HTTP-capable tool
  • Connect your own AI workflows
  • Keep control of when messages are sent
YOUR LOGIC. YOUR WORKFLOW.
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.

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.

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.

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.