mailbridgeAPI
DEMOLog inConnect a mailbox
MAILBOX API RESOURCE CENTRE

Email API guides, integrations and comparisons

Choose a provider, framework, operational problem or comparison. Every guide includes a concrete workflow, copy-ready code, limits and a live demo path.

Integration guide

POST /sendemail/ · GET /getemail/Integration guide

Gmail to API

Connect Gmail or Google Workspace with OAuth 2.0, then send and retrieve email through mailbox-scoped API keys.

Explore feature
Microsoft OAuth · MailBridgeAPI endpointsIntegration guide

Outlook mailbox API

Connect Microsoft 365, Outlook.com or Hotmail and use one HTTP API for mailbox sending and received-message access.

Explore feature
GET /getemail/Integration guide

IMAP REST API

Read a compatible mailbox through an HTTP endpoint instead of rebuilding IMAP connection and pagination logic in every project.

Explore feature
WordPress wp_mail() → MailBridgeAPIIntegration guide

WordPress email API

Route WordPress and WooCommerce mail through one selected mailbox without keeping its SMTP password in the WordPress database.

Explore feature
n8n HTTP Request → MailBridgeAPIIntegration guide

n8n email API

Use HTTP Request nodes to send from or read an existing mailbox while keeping its provider credentials outside every n8n workflow.

Explore feature
Laravel HTTP client → POST /sendemail/Integration guide

Laravel email API

Send through a connected business mailbox from Laravel with an ordinary HTTP request and centralized mailbox configuration.

Explore feature
Python requests → GET /getemail/Integration guide

Python IMAP API

Retrieve mailbox messages as JSON from Python without maintaining a separate IMAP session in every script or worker.

Explore feature
Node.js fetch → MailBridgeAPIIntegration guide

Node.js mailbox API

Send and retrieve email from Node.js with fetch while the mailbox connection remains centrally managed.

Explore feature
Odoo Python → MailBridgeAPIIntegration guide

Odoo email integration

Connect Odoo workflows to an existing business mailbox for controlled sending, received-message processing and centralized monitoring.

Explore feature
Received email → draft → approval → sendIntegration guide

AI email approval workflow

Retrieve incoming email, prepare a controlled reply and require human approval before the connected mailbox sends it.

Explore feature

Honest comparison

Compare connection, operations and ownershipHonest comparison

MailBridgeAPI vs Nylas

Compare a focused MailBridgeAPI mailbox workflow with Nylas connected-account APIs, wider communications features and operating model.

Explore feature
Managed service vs self-hosted infrastructureHonest comparison

MailBridgeAPI vs EmailEngine

Compare a managed mailbox API with a self-hosted email engine, including infrastructure ownership, operations and deployment effort.

Explore feature
Focused mailbox API vs unified messagingHonest comparison

MailBridgeAPI vs Unipile

Compare MailBridgeAPI mailbox operations with a broader unified messaging API designed to combine several communication channels.

Explore feature

Troubleshooting guide

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.