RESPONSIBLE DISCLOSURE

Report a security vulnerability

Send a responsible security report directly to the MailBridgeAPI team without exposing the issue publicly.

1
Email info@mailbridgeapi.com with the subject “Security vulnerability report”.
2
Describe the affected URL or component, prerequisites, reproduction steps and potential impact.
3
Include a minimal proof of concept with secrets and personal data removed.
4
Allow reasonable time for investigation before public disclosure.

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.