mailbridgeAPI
DEMOLog inConnect a mailbox
YOUR SYSTEMS. ONE EMAIL WORKFLOW.

Connect your business tools to every useful email conversation.

Link MailBridgeAPI to any HTTPS API you control or are authorized to use—ERP, CRM, billing, stock, logistics, support or a custom web tool. Configure the connection once in the dashboard, then let your email automation retrieve approved information or trigger approved actions.

Works with one or multiple APIsRead information or run approved actionsPer-mailbox integration selectionHuman approval remains available
Incoming emailalex@customer.com
Identify contactCustomer #1842Approved data only
Your ERP & APIs
ERPCRMAPIWEB
Precise replyRe: Order #1842 Ready
CONNECT WHAT YOU ALREADY USE

Your tools do not need to be replaced.

If a system exposes a secure HTTPS endpoint, MailBridgeAPI can be configured to call it. You define exactly what is available to the email workflow.

ERP & CRM

Customer records, account status, contracts and approved relationship data.

Billing & orders

Invoice status, order details, payment references and customer-specific history.

Stock & logistics

Availability, shipment tracking, lead times and delivery milestones.

Support & web tools

Tickets, appointments, internal services and your own private APIs.

CONFIGURE ONCE IN THE DASHBOARD

From API documentation to a tested integration.

The dashboard keeps configuration focused and testable before it is used in a real conversation.

01

Describe the integration

Give it a clear name and explain when it should be used and how replies should be written.

02

Add endpoints

Set the URL, method, authentication, parameters and the response fields that may be shared with the email assistant.

03

Test the request

Run a controlled test and inspect the response before enabling the integration.

04

Assign it to a mailbox

Choose which connected mailbox may use which integrations, with automatic sending or human approval.

THE RIGHT DATA FOR THE RIGHT CONTACT

Identify the sender before retrieving private information.

Customer-specific workflows can first resolve the verified sender email address into an internal customer ID or reference. Later requests use that reference, helping prevent one contact from receiving another customer’s data.

General information

Prices, opening hours, catalogue data or other public information can be queried without customer identification.

Customer-specific information

Orders, invoices or account details should require a successful identity lookup before another integration is called.

identity.resolve(email){ "customer_id": 1842, "verified": true }
AI GROUNDED IN YOUR BUSINESS DATA

Replies based on live information, not guesses.

When a message requires business data, the email assistant can select an authorized integration, pass the expected parameters and use the permitted result to prepare a clear answer in the contact’s language.

  • Follow the context of an ongoing email thread
  • Use several integrations in one workflow when required
  • Retrieve information with GET-style actions
  • Submit approved updates with POST-style actions
  • Send automatically or place the draft in the approval queue
  • Keep integration-specific instructions for tone and behavior
Incoming emailalex@customer.com
Identify contactCustomer #1842Approved data only
Your ERP & APIs
ERPCRMAPIWEB
Precise replyRe: Order #1842 Ready
PRACTICAL WORKFLOWS

Turn common inbox questions into precise actions.

01

“Where is my order?”

Identify the customer, retrieve the matching shipment and answer with the current delivery status.

Identity → order API → reply
02

“Can you resend my invoice?”

Find the account and invoice reference, then prepare the correct response or approved action.

Identity → billing API → action
03

“What does this service cost?”

Read a public tariff endpoint and answer with current pricing without requiring customer identity.

Pricing API → reply
04

“Please update my appointment.”

Validate the contact, check availability and submit the approved change through your tool.

Identity → calendar API → POST
CONTROL AT EVERY STEP

Useful automation with clear boundaries.

MailBridgeAPI calls only the integrations and endpoints you configure. Keep sensitive decisions under human control while automating routine, verifiable work.

Encrypted authentication configuration
Explicit endpoint and method definitions
Allowlisted response fields
Identity gate for private customer data
Per-mailbox access to integrations
Human review before sending when enabled
CONNECT EMAIL TO YOUR OPERATIONS

Make your mailbox understand the tools behind your business.

Start with one integration and one mailbox, test the complete workflow, then add more endpoints as your needs grow.

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.