# MailBridgeAPI public knowledge

Revision: 84b4718880ca93b8360d3c0a871ab0c776739582e3d35f1bd078d0157afc7222

Updated: 2026-09-05T22:16:50.496Z

Language: en

Public product information and email API documentation. No mailbox contents, customer records, credentials, private infrastructure settings or runtime API responses are indexed.

## What is MailBridgeAPI?

Article ID: product-overview

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T20:04:49.808Z

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.
MailBridgeAPI turns your existing SMTP and IMAP mailbox into an email API. Connect once, then call HTTP endpoints to send and retrieve emails across your projects.
SMTP and IMAP are how email works. You shouldn’t have to rebuild that connection in every project. MailBridgeAPI gives your applications a consistent API while you manage your mailbox settings in one dashboard.
MailBridgeAPI uses your existing email service. It does not replace your email provider or remove its limits. You keep your address and continue using your usual email client.

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

Article ID: password-handoff

Source: https://mailbridgeapi.com/#password-handoff

Updated: 2026-09-04T16:33:27.869Z

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.
Mailbox owner
Enters SMTP / IMAP credentials in MailBridgeAPI.
Uses the configured connection to communicate with the mailbox.
Uses account and mailbox API keys to send or retrieve emails.
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.

## Connect a mailbox and make your first API request

Article ID: getting-started

Source: https://mailbridgeapi.com/services/

Updated: 2026-09-04T16:33:27.869Z

What you’ll need
A mailbox you are authorized to connect
SMTP host, port, username, and credentials
IMAP host, port, username, and credentials
Provider-approved authentication and access settings
Connect your mailbox
Add your SMTP and IMAP settings in the dashboard. Keep using your existing address and email provider.
Get your API keys
Use your account API key and the key for your chosen mailbox. Your application never needs the mailbox password.
Make your first request
Send a message, retrieve your inbox, or connect email to the tools and workflows you already use.
Connect your keys
Paste your account API key and the key for one configured mailbox. Click Connect.
Fetch your inbox
Open “Retrieve emails”, keep INBOX and start 0, then click Fetch emails.
Read the result
HTTP 200 means the server replied. result.error = "0" indicates success; emails are inside result.emaillist.

## Plans, prices, free trial and limits

Article ID: pricing

Source: https://mailbridgeapi.com/pricing/

Updated: 2026-09-04T16:33:27.869Z

All the core tools to connect your mailbox to your application. No per-request pricing to calculate.
Billed monthly. $9 USD per month.
$90 USD billed annually. Equivalent to $7.50 per month.
Two months free compared with monthly billing.
3-day free trial · No credit card required
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.
Published limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.

## Send from your own address

Article ID: feature-sending

Source: https://mailbridgeapi.com/features/#sending

Updated: 2026-09-04T16:33:27.869Z

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

Article ID: feature-receiving

Source: https://mailbridgeapi.com/features/#receiving

Updated: 2026-09-04T16:33:27.869Z

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

Article ID: feature-keys

Source: https://mailbridgeapi.com/features/#keys

Updated: 2026-09-04T16:33:27.869Z

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

Article ID: feature-branding

Source: https://mailbridgeapi.com/features/#branding

Updated: 2026-09-04T16:33:27.869Z

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

Article ID: feature-unsubscribe

Source: https://mailbridgeapi.com/features/#unsubscribe

Updated: 2026-09-04T16:33:27.869Z

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

Article ID: feature-automation

Source: https://mailbridgeapi.com/features/#automation

Updated: 2026-09-04T16:33:27.869Z

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.

## Do I need to change my email provider?

Article ID: faq-1

Source: https://mailbridgeapi.com/#main

Updated: 2026-09-04T16:33:27.869Z

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?

Article ID: faq-2

Source: https://mailbridgeapi.com/#main

Updated: 2026-09-04T16:33:27.869Z

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?

Article ID: faq-3

Source: https://mailbridgeapi.com/#main

Updated: 2026-09-04T16:33:27.869Z

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?

Article ID: faq-4

Source: https://mailbridgeapi.com/#main

Updated: 2026-09-04T16:33:27.869Z

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?

Article ID: faq-5

Source: https://mailbridgeapi.com/#main

Updated: 2026-09-04T16:33:27.869Z

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?

Article ID: faq-6

Source: https://mailbridgeapi.com/#main

Updated: 2026-09-04T16:33:27.869Z

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?

Article ID: faq-7

Source: https://mailbridgeapi.com/#main

Updated: 2026-09-04T16:33:27.869Z

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

## Connect one mailbox to several projects.

Article ID: use-case-multiple-projects

Source: https://mailbridgeapi.com/use-cases/#multiple-projects

Updated: 2026-09-04T16:33:27.869Z

DEVELOPMENT TEAMS
Use the same mailbox across internal tools and applications while managing its connection settings centrally.
Scenario: A website, an invoicing tool, and an operations script all use the same mailbox. A provider setting changes.
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.
Benefit: Mailbox configuration lives in one place. You avoid distributing the mailbox password across each project.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## Build for clients without asking for their email password.

Article ID: use-case-agencies

Source: https://mailbridgeapi.com/use-cases/#agencies

Updated: 2026-09-04T16:33:27.869Z

AGENCIES & FREELANCERS
Connect a client’s mailbox to their website or application using API keys. The client handles the mailbox credentials.
Scenario: 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.
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.
Benefit: A clearer handoff: the client manages the mailbox connection, while the developer works with API access.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## Put email conversations where your team works.

Article ID: use-case-support

Source: https://mailbridgeapi.com/use-cases/#support

Updated: 2026-09-04T16:33:27.869Z

CUSTOMER SUPPORT
Read customer messages inside your support tool and send replies from your existing support address.
Scenario: Your team switches between a shared inbox and an internal support application to handle the same customer requests.
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.
Benefit: Less switching between tools and a customer conversation attached to the work it belongs to.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## Send invoices from the address customers recognize.

Article ID: use-case-invoices

Source: https://mailbridgeapi.com/use-cases/#invoices

Updated: 2026-09-04T16:33:27.869Z

FINANCE & OPERATIONS
Deliver invoices, payment instructions, and follow-ups from your accounting workflow.
Scenario: An invoice is ready in your internal system. Someone still downloads the PDF, opens an email client, and attaches it by hand.
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.
Benefit: Fewer manual steps, consistent email content, and a recognizable sender for your customers.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## Keep customers informed as an order moves forward.

Article ID: use-case-commerce

Source: https://mailbridgeapi.com/use-cases/#commerce

Updated: 2026-09-04T16:33:27.869Z

E-COMMERCE & BOOKINGS
Send order updates, appointment details, and booking confirmations from your own business mailbox.
Scenario: A booking is confirmed or an order changes status in your application. The customer needs the right details at the right moment.
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.
Benefit: Communication follows the business event, using the email identity your customer already knows.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## Turn incoming emails into useful input for your AI tools.

Article ID: use-case-ai

Source: https://mailbridgeapi.com/use-cases/#ai

Updated: 2026-09-04T16:33:27.869Z

AI-ASSISTED WORK
Build email classification, request summaries, and reply drafts around a connected mailbox.
Scenario: Your team receives repetitive enquiries and wants help identifying the topic and preparing a first draft.
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.
Benefit: A practical route from inbox content to assisted work, with human review where you need it.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## Make email a step in your existing workflow.

Article ID: use-case-automations

Source: https://mailbridgeapi.com/use-cases/#automations

Updated: 2026-09-04T16:33:27.869Z

AUTOMATION & INTERNAL TOOLS
Connect an HTTP-capable automation tool to your mailbox for notifications and scheduled processing.
Scenario: An approved request in your business system should trigger an email, or a scheduled workflow needs to collect new inbox messages.
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.
Benefit: Email becomes part of the process instead of a separate task someone has to remember.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## Keep opt-out records connected to your contact list.

Article ID: use-case-contact-lists

Source: https://mailbridgeapi.com/use-cases/#contact-lists

Updated: 2026-09-04T16:33:27.869Z

CUSTOMER COMMUNICATION
Retrieve unsubscribe records and use them to update the mailing list in your own application.
Scenario: Your application sends customer communications and needs to respect recipients who have asked to opt out.
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.
Benefit: Opt-out information becomes part of your list-management workflow, instead of a disconnected record.
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.

## One connection. Value at every level.

Article ID: audiences

Source: https://mailbridgeapi.com/use-cases/

Updated: 2026-09-04T16:33:27.869Z

For mailbox owners
Keep your familiar address and enter your connection settings yourself. A developer can integrate your mailbox without asking for its password.
For developers and agencies
Use account and mailbox API keys in your backend. Reuse the same HTTP integration pattern across client projects.
For business teams
Bring emails into the tools you already work in, and send updates from the address your customers recognize.

## Authentication

Article ID: api-authentication

Source: https://mailbridgeapi.com/doc/#authentication

Updated: 2026-09-04T16:33:27.869Z

Requests require two values: apikey identifies your account; apikeybox selects a configured mailbox. Examples use the documented request parameters. Keep keys in server-side environment variables.
For GET endpoints, query parameters can appear in logs. The published reference also describes Bearer authentication for the account key; verify support in your integration before adopting it.
Identifies your account. Find it in your MailBridgeAPI dashboard.
Selects the mailbox to send from or read. This is the apikeybox value in your dashboard.
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.

## Send an email

Article ID: api-send

Source: https://mailbridgeapi.com/doc/#send

Updated: 2026-09-04T16:33:27.869Z

POST https://api.mailbridgeapi.com/sendemail/
Send an email through the SMTP connection of the selected mailbox. Supports HTML, text, CC recipients, attachments, inline images, and an optional unsubscribe footer.
Parameters:
apikey (Required): Account API key.
apikeybox (Required): API key of the SMTP mailbox to use.
recipient_email (Required): Primary recipient email address.
mail_subject (Required): Email subject.
mail_body (Required): HTML or plain text message body.
sender_email (Optional): Override the sender address; defaults to the SMTP mailbox sender. Your provider must allow the address.
sender_name (Optional): Override the sender display name.
reply_email (Optional): Reply-To address; defaults to sender_email.
reply_name (Optional): Reply-To display name.
email_cc1, email_cc2, email_cc3 (Optional): Up to three CC recipients.
format (Optional): html (default) or text.
charset (Optional): Message character set; defaults to UTF-8.
attachmentBase64_1, attachmentBase64_2 (Optional): Attachment contents encoded as base64.
attachmentBase64_name_1, attachmentBase64_name_2 (Optional): Filenames for the corresponding attachments.
embeddedImage (Optional): Public image URL to embed inline.
embeddedImage_cid (Optional): Content ID referenced in HTML using cid:YOUR_CID.
unsubscribe (Optional): Set to 1 to append the configured unsubscribe footer; default 0.
from_source (Optional): An optional source label for your send.
allow_self_signed (Optional): Set to yes to allow self-signed TLS certificates. Omit for normal certificate validation.
Example response (illustrative, not live mailbox data):
{
  "result": {
    "error": "0",
    "sent": "OK",
    "id": "msg_example"
  }
}
Check result.error = "0" and result.sent = "OK". The SMTP server accepted the send; this does not guarantee delivery to the recipient’s inbox.
Published limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.

## Retrieve emails

Article ID: api-receive

Source: https://mailbridgeapi.com/doc/#receive

Updated: 2026-09-04T16:33:27.869Z

GET https://api.mailbridgeapi.com/getemail/
Read messages from a selected IMAP folder. The result contains a UID-keyed map under result.emaillist. Each page contains up to 30 messages; increment start by 30 to retrieve the next page.
Parameters:
apikey (Required): Account API key.
apikeybox (Required): API key of the connected IMAP mailbox.
mbox (Required): IMAP folder name, such as INBOX, Sent, or Drafts.
start (Optional): Zero-based index; defaults to 0. Up to 30 messages per page.
Example response (illustrative, not live mailbox data):
{
  "result": {
    "error": "0",
    "emaillist": {
      "50123": {
        "id": 50123,
        "object": "Hello%20there",
        "body": "%3Cp%3EHello%3C%2Fp%3E",
        "email1": "jane@example.com",
        "email2": "hello@yourcompany.com",
        "timestamp": 1736505600,
        "date": "10/01/2025 - 09:20:00",
        "size": 42,
        "attachment": null,
        "loop": 0
      }
    }
  }
}
Messages are grouped by their IMAP UID under result.emaillist. Subject (object) and body may be URL-encoded. Decode those fields before displaying them as text.
Published limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.

## Unsubscribe records

Article ID: api-unsubscribe

Source: https://mailbridgeapi.com/doc/#unsubscribe

Updated: 2026-09-04T16:41:42.524Z

GET https://api.mailbridgeapi.com/email/unsubscribed/
Retrieve up to 500 unsubscribe-related send records for a mailbox under result.customer. Optionally filter by recipient email. The start parameter is reserved and may be ignored.
Parameters:
apikey (Required): Account API key.
apikeybox (Required): API key of the SMTP mailbox.
email (Optional): Filter records by recipient email address.
start (Optional): Reserved index; may be ignored by the current implementation.
Example response (illustrative, not live mailbox data):
{
  "result": {
    "error": "0",
    "customer": [
      {
        "recipientEmail": "jane@example.com",
        "subject": "Monthly update",
        "unsubscribeaskedDate": "2025-01-11"
      }
    ]
  }
}
Records are under result.customer. Use recipientEmail to update your list. This endpoint reads opt-out records; it does not unsubscribe a contact itself.
Published limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.

## API responses, errors and troubleshooting

Article ID: api-errors

Source: https://mailbridgeapi.com/doc/#errors

Updated: 2026-09-04T16:33:27.869Z

A 200 HTTP response alone does not mean the email was sent. Inspect result.error and result.sent before treating an SMTP request as successful.
200: Request processed. Inspect result.error for the provider result.
400: Required parameters are missing.
401: Invalid or expired API key, or a deactivated account.
500: SMTP / IMAP provider failure or an internal error.
401 / invalid key: Check both keys, the selected mailbox, and the account’s active status.
SMTP connection failure: Check SMTP host, port, authentication, and sender permissions in the dashboard.
IMAP connection failure: Check IMAP access, credentials, and the exact folder name.
No messages returned: Try INBOX with start = 0. The folder may be empty.
Timeout after sending: Check your dashboard or Sent folder before retrying. The send may already have happened.
The send result is unknown. Check the mailbox or dashboard before trying again to avoid sending a duplicate.

## Try the API with your mailbox

Article ID: api-explorer

Source: https://mailbridgeapi.com/doc/#api-connection

Updated: 2026-09-04T16:33:27.869Z

Connect your account key, choose a mailbox, then run a request below. These requests use the live MailBridgeAPI service.
Your key is ready to use. The API checks it when you run your first request.
Keys stay in this page’s memory and are cleared on disconnect or reload. Requests pass through this website’s server to MailBridgeAPI.
This is a live send, not a simulation. Your provider’s sending limits apply.
I understand this sends a real email to the recipient entered above.
The explorer accepts up to 1 MB per request. Keep test attachments small.
The response is displayed as text. Email HTML and attachments are never executed.

## Company and contact

Article ID: company-and-contact

Source: https://mailbridgeapi.com/about-us/

Updated: 2026-09-04T16:33:27.869Z

MailBridgeAPI is a service by APPHUBIC LTD.
20 Wenlock Road, London, England, N1 7GU
Company number 16438256
For product questions, account help, and integration support.
info@mailbridgeapi.com

## Create your MailBridgeAPI account

Article ID: create-account

Source: https://mailbridgeapi.com/signup/

Updated: 2026-09-04T19:56:04.468Z

Create your secure workspace, connect a mailbox, and use its API key in every project. No credit card is required for the trial.
You will receive an account ID and licence after registration.
Your SMTP and IMAP passwords stay in the dashboard.
Projects use a revocable API key instead of mailbox credentials.
Change a mailbox password once without updating every integration.
3-day trial · No credit card · Cancel anytime

## Sign in to your MailBridgeAPI account

Article ID: account-sign-in

Source: https://mailbridgeapi.com/connect/

Updated: 2026-09-04T19:56:04.468Z

Use your account ID and licence to open the dashboard and manage mailboxes, API keys, email activity, and automations.
Enter the credentials provided when your account was created.
Manage SMTP and IMAP connections centrally.
Keep mailbox passwords out of projects and repositories.
Review email activity and ChatGPT mailbox settings.
Encrypted connection · Private dashboard · Central access

## Turn a standard email mailbox into an API.

Article ID: mailbox-to-api

Source: https://mailbridgeapi.com/#mailbox-to-api

Updated: 2026-09-04T20:08:42.357Z

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.
POST /sendemail/
Send email
Trigger an API request to send from your connected address.
GET /getemail/
Retrieve email
Read messages from the connected mailbox through a JSON response.
GET /email/unsubscribed/
Sync unsubscribes
Retrieve opt-out records for your own contact workflows.

## Turn your mobile phone into an SMS and call API.

Article ID: smsmobileapi-overview

Source: https://mailbridgeapi.com/smsmobileapi/

Updated: 2026-09-05T16:05:28.291Z

SMSMobileAPI connects a mobile phone to your applications through a REST API. Send SMS through the connected phone, retrieve received messages, and bring missed, incoming, and outgoing call activity into your workflows.
SMS and call operations pass through the SMSMobileAPI mobile app installed on the connected phone.
Connect real mobile activity to the tools you already use.
Use the phone and mobile number that belong to your workflow. The app creates the bridge between the device, the SMSMobileAPI dashboard, and your software.
Send SMS through an API
Trigger an API request and let the connected phone send the message through its mobile service.
Retrieve received SMS
Bring incoming SMS into a CRM, support tool, automation, or your own application.
Retrieve call activity
Access synchronized missed calls, answered incoming calls, and outgoing calls through documented endpoints.
Build with your own phone
Keep the mobile device and number at the center of the workflow while your applications communicate through an API key.
A simple bridge in three steps.
Install the mobile app
Install SMSMobileAPI on the phone that will connect to your workflow.
Connect the device
Link the phone to your account and obtain the API credentials used by your backend.
Call the endpoints
Send SMS or retrieve SMS and supported call activity from your application.
Email for one project. Mobile communication for the next.
MailBridgeAPI: Connect an existing SMTP and IMAP mailbox to endpoints for sending and retrieving email.
SMSMobileAPI: Connect a mobile phone to endpoints for SMS and synchronized mobile call activity.
Feature availability and synchronization depend on the connected device, operating-system permissions, network access, and the installed app version. Call synchronization is documented for the Android app.

## Service policy questions

Article ID: service-policy-status

Source: https://mailbridgeapi.com/terms-and-conditions-of-sale/

Updated: 2026-09-04T16:33:27.869Z

The published legacy legal texts require review. Do not infer refund, cancellation, retention, encryption or compliance guarantees from this knowledge base. Refer questions about service policies to info@mailbridgeapi.com and the linked policy pages.

## credentialRotation

Article ID: reference-use-cases-credentialRotation

Source: https://mailbridgeapi.com/doc/

Updated: 2026-09-04T18:07:03.910Z

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.
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 settings
Update 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.
Give projects API access, never the mailbox password.
Developers, other teams and applications work with account and mailbox API keys. The SMTP/IMAP password remains in the MailBridgeAPI dashboard and does not need to be copied into those projects.
API keys can access email operations. Keep them in server-side environment variables or a secret manager; never expose them in a public repository or browser code.

## Complete pricing reference

Article ID: reference-pricing

Source: https://mailbridgeapi.com/pricing/

Updated: 2026-09-04T17:46:19.414Z

Simple pricing for your email API.
ONE SERVICE. EVERYTHING YOU NEED.
All the core tools to connect your mailbox to your application. No per-request pricing to calculate.
MailBridgeAPI
Your complete email-to-API toolkit.
Billed monthly. $9 USD per month.
$90 USD billed annually. Equivalent to $7.50 per month.
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.
Everything you need, in either plan.
Feature
Included
3-day free trial · No credit card required
Your pricing questions, answered.
Two months free compared with monthly billing.

## Complete product reference

Article ID: reference-product

Source: https://mailbridgeapi.com/services/

Updated: 2026-09-04T20:04:49.808Z

MEET YOUR EMAIL’S NEW SUPERPOWER.
Connect your mailbox to an email API.
MailBridgeAPI turns your existing SMTP and IMAP mailbox into an email API. Connect once, then call HTTP endpoints to send and retrieve emails across your projects.
Keep the mailbox. Simplify the integration.
SMTP and IMAP are how email works. You shouldn’t have to rebuild that connection in every project. MailBridgeAPI gives your applications a consistent API while you manage your mailbox settings in one dashboard.
Your mailbox stays yours.
MailBridgeAPI uses your existing email service. It does not replace your email provider or remove its limits. You keep your address and continue using your usual email client.
What you’ll need
A mailbox you are authorized to connect
SMTP host, port, username, and credentials
IMAP host, port, username, and credentials
Provider-approved authentication and access settings
One mailbox, multiple projects. Update its connection settings in one place.

## Complete features reference

Article ID: reference-features

Source: https://mailbridgeapi.com/features/

Updated: 2026-09-04T16:33:27.869Z

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.

## Complete faq reference

Article ID: reference-faq

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:33:27.869Z

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.

## Complete docs reference

Article ID: reference-docs

Source: https://mailbridgeapi.com/doc/

Updated: 2026-09-04T20:04:49.808Z

MAILBRIDGEAPI / DOCUMENTATION
Email API documentation: SMTP and IMAP.
Turn an SMTP and IMAP mailbox into an API. Call HTTP endpoints to send messages, retrieve your inbox, and manage unsubscribe records.
Overview
Quick start
Authentication
Send an email
Retrieve emails
Unsubscribe records
Responses & errors
Rate limits
Base URL
API v1
Before your first request
Create your account and connect your SMTP / IMAP mailbox in the dashboard.
Copy your account API key and the API key for your mailbox.
Use these keys in a request from your server. Keep real keys out of browsers, source control, and public logs.
Requests require two values: apikey identifies your account; apikeybox selects a configured mailbox. Examples use the documented request parameters. Keep keys in server-side environment variables.
For GET endpoints, query parameters can appear in logs. The published reference also describes Bearer authentication for the account key; verify support in your integration before adopting it.
Send an email through the SMTP connection of the selected mailbox. Supports HTML, text, CC recipients, attachments, inline images, and an optional unsubscribe footer.
Read messages from a selected IMAP folder. The result contains a UID-keyed map under result.emaillist. Each page contains up to 30 messages; increment start by 30 to retrieve the next page.
Retrieve up to 500 unsubscribe-related send records for a mailbox under result.customer. Optionally filter by recipient email. The start parameter is reserved and may be ignored.
Parameter
Required
Optional
Description
Request example
Example response
A 200 HTTP response alone does not mean the email was sent. Inspect result.error and result.sent before treating an SMTP request as successful.
200
Request processed. Inspect result.error for the provider result.
400
Required parameters are missing.
401
Invalid or expired API key, or a deactivated account.
500
SMTP / IMAP provider failure or an internal error.
Published limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.
Examples follow the published MailBridgeAPI v1 reference. Code samples are illustrative; the interactive explorer sends live requests only when you run a test.
Copy base URL

## Complete about reference

Article ID: reference-about

Source: https://mailbridgeapi.com/about-us/

Updated: 2026-09-04T17:46:19.414Z

A MORE USEFUL CONNECTION.
About MailBridgeAPI.
MailBridgeAPI helps developers and businesses turn existing email accounts into programmable tools.
Email is already part of your business.
The next step is making it part of your applications. Our approach is simple: keep the mailbox you trust, connect its SMTP and IMAP settings once, and give your projects a consistent API to work with.
Built for people who build.
From a small internal script to a customer-facing application, the goal is the same: less repeated email configuration, clearer integrations, and more time to work on the parts that make your product useful.
The company behind the bridge
MailBridgeAPI is a service by APPHUBIC LTD.
20 Wenlock Road, London, England, N1 7GU
Company number 16438256

## Complete use cases reference

Article ID: reference-use-cases

Source: https://mailbridgeapi.com/use-cases/

Updated: 2026-09-04T18:07:03.910Z

ONE MAILBOX. MANY WAYS TO BUILD.
Email API use cases for your business.
From a client website to a customer support workflow, connect the email address you already use to the work you need to get done.
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
See how it works
Imagine this
How you build it
What your team gains
Explore the endpoint
These are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.
One connection. Value at every level.
For mailbox owners
Keep your familiar address and enter your connection settings yourself. A developer can integrate your mailbox without asking for its password.
For developers and agencies
Use account and mailbox API keys in your backend. Reuse the same HTTP integration pattern across client projects.
For business teams
Bring emails into the tools you already work in, and send updates from the address your customers recognize.
DEVELOPMENT TEAMS
Connect one mailbox to several projects.
Use the same mailbox across internal tools and applications while managing its connection settings centrally.
A website, an invoicing tool, and an operations script all use the same mailbox. A provider setting changes.
Configure the mailbox’s SMTP and IMAP access in MailBridgeAPI.
Your authorized projects use the account and mailbox keys for their requests.
Update the mailbox connection in the dashboard when its provider settings change.
Mailbox configuration lives in one place. You avoid distributing the mailbox password across each project.
send
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.
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.
The client enters their SMTP and IMAP settings in the MailBridgeAPI dashboard.
They provide the account API key and the key for the mailbox to the authorized developer.
The developer keeps those keys in the project’s server configuration and sends acknowledgements through the API.
A clearer handoff: the client manages the mailbox connection, while the developer works with API access.
send
CUSTOMER SUPPORT
Put email conversations where your team works.
Read customer messages inside your support tool and send replies from your existing support address.
Your team switches between a shared inbox and an internal support application to handle the same customer requests.
Your application fetches messages from the support mailbox’s INBOX.
It associates messages with customer records or tickets using your own matching rules.
An agent writes a response in your tool; your backend sends it through the connected mailbox.
Less switching between tools and a customer conversation attached to the work it belongs to.
receive
FINANCE & OPERATIONS
Send invoices from the address customers recognize.
Deliver invoices, payment instructions, and follow-ups from your accounting workflow.
An invoice is ready in your internal system. Someone still downloads the PDF, opens an email client, and attaches it by hand.
Your application generates the invoice and prepares the recipient and message.
It encodes the PDF attachment and calls the sending endpoint.
It checks the API’s SMTP result and records that result against the invoice.
Fewer manual steps, consistent email content, and a recognizable sender for your customers.
send
E-COMMERCE & BOOKINGS
Keep customers informed as an order moves forward.
Send order updates, appointment details, and booking confirmations from your own business mailbox.
A booking is confirmed or an order changes status in your application. The customer needs the right details at the right moment.
Your application detects the order or booking event.
It prepares an email using the customer’s details and the event information.
Your backend sends the message through MailBridgeAPI and checks the send result.
Communication follows the business event, using the email identity your customer already knows.
send
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.
Your team receives repetitive enquiries and wants help identifying the topic and preparing a first draft.
Your backend retrieves the relevant messages through the IMAP endpoint.
Your chosen AI service summarizes or classifies the content according to your rules.
Your team reviews a draft before your application sends the approved response.
A practical route from inbox content to assisted work, with human review where you need it.
receive
AUTOMATION & INTERNAL TOOLS
Make email a step in your existing workflow.
Connect an HTTP-capable automation tool to your mailbox for notifications and scheduled processing.
An approved request in your business system should trigger an email, or a scheduled workflow needs to collect new inbox messages.
Configure a scheduled job or an event in your application or automation tool.
Use its HTTP request step with your account and mailbox keys.
Process the JSON response and decide what the next step should do.
Email becomes part of the process instead of a separate task someone has to remember.
send
CUSTOMER COMMUNICATION
Keep opt-out records connected to your contact list.
Retrieve unsubscribe records and use them to update the mailing list in your own application.
Your application sends customer communications and needs to respect recipients who have asked to opt out.
Configure the unsubscribe footer and enable it on the relevant sends.
Retrieve unsubscribe records for the mailbox through the API.
Match those recipients to your contact list and exclude them from future applicable mailings.
Opt-out information becomes part of your list-management workflow, instead of a disconnected record.
unsubscribe

## Complete password handoff reference

Article ID: reference-password-handoff

Source: https://mailbridgeapi.com/#password-handoff

Updated: 2026-09-04T16:37:57.496Z

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.
Build email integrations without asking your client for their mailbox password.
Mailbox owner
Enters SMTP / IMAP credentials in MailBridgeAPI.
MailBridgeAPI
Uses the configured connection to communicate with the mailbox.
Developer & application
Uses account and mailbox API keys to send or retrieve emails.
MAILBOX CREDENTIALS
API KEYS
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.
See the client integration example

## livechat website reference

Article ID: reference-site-livechat

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T18:33:50.038Z

AI support chat
The website offers an AI assistant powered by OpenAI. It answers product and integration questions using the current MailBridgeAPI knowledge base and links to supporting pages. It cannot access your account or mailbox, or send email.
To start the AI chat, your name and email address are required and stored by MailBridgeAPI with the conversation. Your messages, recent conversation context and selected public documentation are sent to OpenAI to generate replies; your name and email address are not included in that model context. MailBridgeAPI also stores the language, page, browser information, a pseudonymized network identifier, timestamps, selected sources, token usage, errors and estimated costs for support administration. Conversations are retained on the service server until removed by the operator; they are not added to the public knowledge base. Do not share passwords, API keys or private email content. Contact info@mailbridgeapi.com about your data.
Opening the chat sets a functional HttpOnly cookie, mb_chat, valid for 30 days, to restore your own conversation. Signing into the private webmaster area sets mb_webmaster for up to 8 hours. These cookies are not used for advertising. Clearing cookies removes the browser link to your conversation but does not delete the server history.

## featurePage website reference

Article ID: reference-site-featurePage

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T17:46:19.414Z

BUILT AROUND YOUR MAILBOX.
Email API features for your daily workflows.
The building blocks for email-enabled applications: sending, reading, mailbox access, and consistent communication.

## contact website reference

Article ID: reference-site-contact

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T17:36:14.283Z

LET’S CONNECT.
Real questions. Human answers.
Need help connecting a mailbox, choosing a plan, or finding the right endpoint? Tell us what you’re building.
Email our team
For product questions, account help, and integration support.
Prefer to start with the docs?
Explore authentication, endpoints, parameters, and working request examples.
Tell us about your project
Your name
Work email
What can we help with?
Your message
Alex Morgan
alex@company.com
Tell us what you’re building or where you’re stuck…
Integration question
Account and billing
Product question
Something else
Send message
Your request is sent directly to our team. You do not need an email application.
Your request has been received. Reference:
Your name, email and message are stored privately so our team can handle your request. Do not include passwords or API keys.
Sending…
We could not confirm receipt. Please try again; your message has been kept.
Too many requests. Please try again in an hour.

## cta website reference

Article ID: reference-site-cta

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T20:04:49.808Z

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.
Read the documentation

## notFound website reference

Article ID: reference-site-notFound

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

404 / NOT FOUND
This connection leads nowhere.
The page may have moved. Let’s get you back to the right place.

## eyebrow home reference

Article ID: reference-home-eyebrow

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

YOUR MAILBOX. NOW PROGRAMMABLE.

## title home reference

Article ID: reference-home-title

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

Your email.
Your workflow.
One simple API.

## description home reference

Article ID: reference-home-description

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T20:04:49.808Z

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.

## visual home reference

Article ID: reference-home-visual

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

FROM YOUR INBOX TO YOUR APPLICATION
Your existing mailbox
Connected
Secure connection
API key
your-next-big-idea.js
Your mailbox. Connected to your code.
Less configuration.
More creation.

## providers home reference

Article ID: reference-home-providers

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

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

## features home reference

Article ID: reference-home-features

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T20:04:49.808Z

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.

## steps home reference

Article ID: reference-home-steps

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

THREE STEPS. ENDLESS POSSIBILITIES.
From inbox to integration.
A familiar mailbox on one side. Your next great idea on the other.
Connect your mailbox
Add your SMTP and IMAP settings in the dashboard. Keep using your existing address and email provider.
SMTP + IMAP
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
Make your first request
Send a message, retrieve your inbox, or connect email to the tools and workflows you already use.
HTTP REQUEST → EMAIL

## developer home reference

Article ID: reference-home-developer

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

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

## pricing home reference

Article ID: reference-home-pricing

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

SIMPLE BY DESIGN.
Small price. Full possibility.
One complete feature set. Choose the billing cycle that works for you.

## faqTitle home reference

Article ID: reference-home-faqTitle

Source: https://mailbridgeapi.com/

Updated: 2026-09-04T16:37:57.496Z

A few things you might be wondering.