POST /sendemail/ · GET /getemail/Integration guideGmail to API
Connect Gmail or Google Workspace with OAuth 2.0, then send and retrieve email through mailbox-scoped API keys.
Explore featureChoose a provider, framework, operational problem or comparison. Every guide includes a concrete workflow, copy-ready code, limits and a live demo path.
POST /sendemail/ · GET /getemail/Integration guideConnect Gmail or Google Workspace with OAuth 2.0, then send and retrieve email through mailbox-scoped API keys.
Explore featureMicrosoft OAuth · MailBridgeAPI endpointsIntegration guideConnect Microsoft 365, Outlook.com or Hotmail and use one HTTP API for mailbox sending and received-message access.
Explore featureGET /getemail/Integration guideRead a compatible mailbox through an HTTP endpoint instead of rebuilding IMAP connection and pagination logic in every project.
Explore featurePOST /sendemail/Integration guideKeep your current sender address and provider while applications send through a stable HTTPS endpoint and mailbox key.
Explore featureWordPress wp_mail() → MailBridgeAPIIntegration guideRoute WordPress and WooCommerce mail through one selected mailbox without keeping its SMTP password in the WordPress database.
Explore featureGET /email/activity/Integration guideIdentify WooCommerce as the sending source, inspect accepted and failed messages, and keep mailbox health visible from the dashboard and mobile app.
Explore featuren8n HTTP Request → MailBridgeAPIIntegration guideUse HTTP Request nodes to send from or read an existing mailbox while keeping its provider credentials outside every n8n workflow.
Explore featureLaravel HTTP client → POST /sendemail/Integration guideSend through a connected business mailbox from Laravel with an ordinary HTTP request and centralized mailbox configuration.
Explore featurePython requests → GET /getemail/Integration guideRetrieve mailbox messages as JSON from Python without maintaining a separate IMAP session in every script or worker.
Explore featureNode.js fetch → MailBridgeAPIIntegration guideSend and retrieve email from Node.js with fetch while the mailbox connection remains centrally managed.
Explore featureOdoo Python → MailBridgeAPIIntegration guideConnect Odoo workflows to an existing business mailbox for controlled sending, received-message processing and centralized monitoring.
Explore featureReceived email → draft → approval → sendIntegration guideRetrieve incoming email, prepare a controlled reply and require human approval before the connected mailbox sends it.
Explore featureGET /mailbox/status/ · mobile push alertsIntegration guideMonitor mailbox readiness, record delivery errors and receive mobile alerts when a business mailbox needs attention.
Explore featureCompare connection, operations and ownershipHonest comparisonCompare a focused MailBridgeAPI mailbox workflow with Nylas connected-account APIs, wider communications features and operating model.
Explore featureManaged service vs self-hosted infrastructureHonest comparisonCompare a managed mailbox API with a self-hosted email engine, including infrastructure ownership, operations and deployment effort.
Explore featureFocused mailbox API vs unified messagingHonest comparisonCompare MailBridgeAPI mailbox operations with a broader unified messaging API designed to combine several communication channels.
Explore featureLocal SMTP credentials vs centralized API keysHonest comparisonCompare storing SMTP settings inside every application with central mailbox management and API-based delivery.
Explore featureExisting mailbox identity vs dedicated sending infrastructureHonest comparisonUnderstand when an API over an existing mailbox fits better than a dedicated transactional sender and when the opposite is true.
Explore featureWordPress log → provider response → recipientTroubleshooting guideDiagnose the difference between WordPress handing off a message, an SMTP provider accepting it and the recipient actually receiving it.
Explore featureNotification configuration → delivery resultTroubleshooting guideCheck notification settings, recipients, message type and authenticated delivery when only customer-facing WordPress email fails.
Explore featureUpdate mailbox once · keep site API keysTroubleshooting guideCentralize one mailbox connection so a provider password change does not require editing every authorized WordPress installation.
Explore featureWordPress source → activity log → mobile controlTroubleshooting guideKeep WordPress sending errors and mailbox connection health visible when you are away from the WordPress administration panel.
Explore featureMailBridgeAPI 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 docsapikey + apikeyboxAPI endpoint requestAction through that mailboxPOST /sendemail/A POST request uses the SMTP connection of the mailbox selected by apikeybox and sends from that mailbox.
GET /getemail/A GET request uses the same mailbox key to retrieve messages from its configured IMAP folders.
YOUR LOGIC. YOUR WORKFLOW.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.