YOUR MAILBOX. NOW PROGRAMMABLE.
Your email.
Your workflow.
One simple API.
Connect your own compatible SMTP and IMAP mailbox to an account API key and a mailbox API key. Your applications use those keys to send requests that act through that same mailbox—send from your address, retrieve received email, and automate workflows—without putting the mailbox password in project code.
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
ConnectedSMTPIMAP
Secure connection
MailBridgeAPIAPI key
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.
MailBridgeAPIMailbox API key
Linked and readymbox_••••7F3APOST /sendemail/GET /getemail/GET /email/unsubscribed/WebsiteCRMAutomation
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.
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.
SMTP operational
Test the outgoing connection used by your applications.
IMAP operational
Test access to incoming messages and folders.
Sending errors visible
Open the activity log, identify the reason and act quickly.
Email carries customer requests, confirmations, invoices and alerts. Its availability should never be left to guesswork.
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.
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 featureBring your inbox into your app
Retrieve incoming messages from your IMAP folders. Turn customer requests, alerts, and replies into useful application data.
Explore featureIntegrate 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 featureTHREE 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 + IMAP02
Get your API keys
MailBridgeAPI links your account API key and a mailbox API key to the mailbox you selected. Your application never needs the mailbox password.
API KEY + MAILBOX KEY03
Make your first request
Call an endpoint with both API keys. The request sends from or reads the same mailbox selected by the mailbox key.
HTTP REQUEST → EMAILONE 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
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
<?php
$payload = [
'apikey' => getenv('MAILBRIDGE_API_KEY'),
'apikeybox' => getenv('MAILBRIDGE_BOX_KEY'),
'recipient_email' => 'jane@example.com',
'mail_subject' => 'Hello, possibilities.',
'mail_body' => 'Your next idea starts here.',
'format' => 'text',
];
$ch = curl_init('https://api.mailbridgeapi.com/sendemail/');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_POSTFIELDS => http_build_query($payload),
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 30,
]);
$response = curl_exec($ch);
if ($response === false) {
$message = curl_error($ch);
curl_close($ch);
throw new RuntimeException($message);
}
curl_close($ch);
$data = json_decode($response, true, 512, JSON_THROW_ON_ERROR);
// Check $data['result']['error'], not only the HTTP status.
print_r($data);Example only — no live requests
ONE MAILBOX. MANY WAYS TO BUILD.
Real work. Real reasons to connect.
One mailbox connection, two API keys, and clear requests for the developer, the team, and the mailbox owner.
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 pricingUp to
2connected mailboxes
Starter
/ month
- Full access to MailBridgeAPI
- Unlimited email API requests
- SMTP sending and IMAP retrieval
- Dashboard and API key management
Up to
5connected mailboxes
Team
/ month
- Full access to MailBridgeAPI
- Unlimited email API requests
- SMTP sending and IMAP retrieval
- Dashboard and API key management
Up to
10connected mailboxes
Business
/ month
- Full access to MailBridgeAPI
- Unlimited email API requests
- SMTP sending and IMAP retrieval
- Dashboard and API key management
Up to
25connected mailboxes
Scale
/ month
- Full access to MailBridgeAPI
- Unlimited email API requests
- SMTP sending and IMAP retrieval
- Dashboard and API key management
More than 25 mailboxes
Unlimited
Managing a larger email fleet? Contact us for an unlimited plan adapted to your monitoring and support needs.
Endpoint rate limits and your email provider’s sending policies apply.
3-day free trial · No credit card required
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