Credential separation
Applications use an account API key and a mailbox API key. Mailbox passwords and OAuth tokens are never intended for public client-side code.
Understand how MailBridgeAPI separates mailbox credentials, API access, account protection and public documentation.
Applications use an account API key and a mailbox API key. Mailbox passwords and OAuth tokens are never intended for public client-side code.
Production website, dashboard and API traffic uses HTTPS. Provider connections use the encryption modes selected for the mailbox configuration.
Gmail, Microsoft, Yahoo and Zoho access and refresh tokens are encrypted at rest with AES-256-GCM using private server-side encryption keys.
The official plugin never stores the dashboard password or mailbox password. Selected API credentials are encrypted locally with a key derived from WordPress authentication salts.
The dashboard supports login history, two-factor authentication and recovery codes. Sessions and access can be revoked.
Only the data required to provide the requested email, activity, support, monitoring or billing operation should be submitted.
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 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.