{ "schemaVersion": "1.0", "name": "MailBridgeAPI public knowledge", "version": "84b4718880ca93b8360d3c0a871ab0c776739582e3d35f1bd078d0157afc7222", "updatedAt": "2026-09-05T22:16:50.496Z", "language": "en", "siteUrl": "https://mailbridgeapi.com", "articleCount": 62, "categories": [ "product", "security", "getting-started", "pricing", "features", "faq", "use-cases", "api", "company", "ecosystem", "policies", "reference" ], "scope": "Public product information and email API documentation. No mailbox contents, customer records, credentials, private infrastructure settings or runtime API responses are indexed.", "articles": [ { "id": "product-overview", "title": "What is MailBridgeAPI?", "category": "product", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "Turn a standard SMTP and IMAP mailbox into an email API. Your applications can call clear HTTP endpoints to send, receive, and automate email from your own address—without sharing the mailbox password with your developer. MailBridgeAPI turn", "content": "Turn a standard SMTP and IMAP mailbox into an email API. Your applications can call clear HTTP endpoints to send, receive, and automate email from your own address—without sharing the mailbox password with your developer.\nMailBridgeAPI turns your existing SMTP and IMAP mailbox into an email API. Connect once, then call HTTP endpoints to send and retrieve emails across your projects.\nSMTP and IMAP are how email works. You shouldn’t have to rebuild that connection in every project. MailBridgeAPI gives your applications a consistent API while you manage your mailbox settings in one dashboard.\nMailBridgeAPI uses your existing email service. It does not replace your email provider or remove its limits. You keep your address and continue using your usual email client.", "tags": [ "email", "mailbox", "SMTP", "IMAP" ], "contentHash": "9f4d13d4f982707da5975186fbd2de4d3f3843085a707982350e8f19cfabdf26", "updatedAt": "2026-09-04T20:04:49.808Z" }, { "id": "password-handoff", "title": "Integrate the mailbox. Keep its password out of the project.", "category": "security", "language": "en", "url": "https://mailbridgeapi.com/#password-handoff", "summary": "Your client or mailbox owner connects the email account in MailBridgeAPI. You build the integration with API keys, without needing to know their mailbox password. Mailbox owner Enters SMTP / IMAP credentials in MailBridgeAPI. Uses the confi", "content": "Your client or mailbox owner connects the email account in MailBridgeAPI. You build the integration with API keys, without needing to know their mailbox password.\nMailbox owner\nEnters SMTP / IMAP credentials in MailBridgeAPI.\nUses the configured connection to communicate with the mailbox.\nUses account and mailbox API keys to send or retrieve emails.\nA more reassuring client handoff\nThe owner enters the mailbox credentials. The developer receives the API access needed for the integration.\nFewer places to share a password\nKeep the mailbox password out of project source code, developer messages, and individual application configurations.\nOne place for connection settings\nWhen mailbox settings change, update the connection in the dashboard instead of redistributing the password across projects.\nMailBridgeAPI still needs the owner’s mailbox credentials to connect to the email provider. API keys grant access to email operations: treat them as secrets and keep them in your backend.", "tags": [ "password", "credentials", "security", "developer", "client", "api key" ], "contentHash": "5a2836b5ea9f4ed7b902369fafe099cdef3e4f8c084c891bd16dfbe166b04203", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "getting-started", "title": "Connect a mailbox and make your first API request", "category": "getting-started", "language": "en", "url": "https://mailbridgeapi.com/services/", "summary": "What you’ll need A mailbox you are authorized to connect SMTP host, port, username, and credentials IMAP host, port, username, and credentials Provider-approved authentication and access settings Connect your mailbox Add your SMTP and IMAP ", "content": "What you’ll need\nA mailbox you are authorized to connect\nSMTP host, port, username, and credentials\nIMAP host, port, username, and credentials\nProvider-approved authentication and access settings\nConnect your mailbox\nAdd your SMTP and IMAP settings in the dashboard. Keep using your existing address and email provider.\nGet your API keys\nUse your account API key and the key for your chosen mailbox. Your application never needs the mailbox password.\nMake your first request\nSend a message, retrieve your inbox, or connect email to the tools and workflows you already use.\nConnect your keys\nPaste your account API key and the key for one configured mailbox. Click Connect.\nFetch your inbox\nOpen “Retrieve emails”, keep INBOX and start 0, then click Fetch emails.\nRead the result\nHTTP 200 means the server replied. result.error = \"0\" indicates success; emails are inside result.emaillist.", "tags": [], "contentHash": "5cdb541fb5b5aa37ab609b9427ee9d82a1a2bf1cbedf4661f5130c014cb6f6c2", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "pricing", "title": "Plans, prices, free trial and limits", "category": "pricing", "language": "en", "url": "https://mailbridgeapi.com/pricing/", "summary": "All the core tools to connect your mailbox to your application. No per-request pricing to calculate. Billed monthly. $9 USD per month. $90 USD billed annually. Equivalent to $7.50 per month. Two months free compared with monthly billing. 3-", "content": "All the core tools to connect your mailbox to your application. No per-request pricing to calculate.\nBilled monthly. $9 USD per month.\n$90 USD billed annually. Equivalent to $7.50 per month.\nTwo months free compared with monthly billing.\n3-day free trial · No credit card required\nFull access to MailBridgeAPI\nUnlimited email API requests\nSMTP sending and IMAP retrieval\nDashboard and API key management\nHeaders, footers, and unsubscribe tools\nPriority support\nEndpoint rate limits and your email provider’s sending policies apply.\nPublished limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.", "tags": [ "price", "cost", "subscription", "trial", "monthly", "annual" ], "contentHash": "d51200a02471854143c8e1901e7ea5a59004288a4eb87856921c951427c277e2", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "feature-sending", "title": "Send from your own address", "category": "features", "language": "en", "url": "https://mailbridgeapi.com/features/#sending", "summary": "Send transactional emails and notifications through your connected SMTP mailbox. Your provider and sender identity stay with you. HTML or plain text messages Custom sender and reply-to names CC recipients and base64 attachments POST /sendem", "content": "Send transactional emails and notifications through your connected SMTP mailbox. Your provider and sender identity stay with you.\nHTML or plain text messages\nCustom sender and reply-to names\nCC recipients and base64 attachments\nPOST /sendemail/", "tags": [], "contentHash": "f5e20c11c6b0d424815f34d30ed3470536cebd92bba315ca3d70560fce949941", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "feature-receiving", "title": "Bring your inbox into your app", "category": "features", "language": "en", "url": "https://mailbridgeapi.com/features/#receiving", "summary": "Retrieve incoming messages from your IMAP folders. Turn customer requests, alerts, and replies into useful application data. Select an IMAP folder Retrieve up to 30 messages per page Work with a JSON response GET /getemail", "content": "Retrieve incoming messages from your IMAP folders. Turn customer requests, alerts, and replies into useful application data.\nSelect an IMAP folder\nRetrieve up to 30 messages per page\nWork with a JSON response\nGET /getemail", "tags": [], "contentHash": "a3d927b62406c81750cc3aeed56610c44505b00d9980621762b565f5c2063a5d", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "feature-keys", "title": "Integrate without the mailbox password", "category": "features", "language": "en", "url": "https://mailbridgeapi.com/features/#keys", "summary": "The mailbox owner enters their credentials in MailBridgeAPI. Your developer uses API keys to connect the project, without needing to know the email password. The owner configures the mailbox connection Your backend uses account and mailbox ", "content": "The mailbox owner enters their credentials in MailBridgeAPI. Your developer uses API keys to connect the project, without needing to know the email password.\nThe owner configures the mailbox connection\nYour backend uses account and mailbox keys\nMailbox passwords stay out of project code\napikey + apikeybox", "tags": [], "contentHash": "bf4bca9af1c93b85880b81cdb8d5254d7dc7254e6549a48d3d81126f16ce733f", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "feature-branding", "title": "Consistent emails, by default", "category": "features", "language": "en", "url": "https://mailbridgeapi.com/features/#branding", "summary": "Configure a shared header and footer in the dashboard. Keep your branding and signature consistent across the emails your applications send. Reusable headers and footers Company signatures and disclaimers Update content from your dashboard ", "content": "Configure a shared header and footer in the dashboard. Keep your branding and signature consistent across the emails your applications send.\nReusable headers and footers\nCompany signatures and disclaimers\nUpdate content from your dashboard\nCONFIGURE ONCE", "tags": [], "contentHash": "0c7d1a96630490dd3f89ea226447693aaba49a65e0ac7dd7aed04b88f21a9e25", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "feature-unsubscribe", "title": "Keep your contact lists in sync", "category": "features", "language": "en", "url": "https://mailbridgeapi.com/features/#unsubscribe", "summary": "Enable unsubscribe links for your mailings and retrieve opt-out records through the API to update your own contact lists. Optional unsubscribe footer Recipient-specific opt-out links Retrieve unsubscribe records by mailbox GET /email/unsubs", "content": "Enable unsubscribe links for your mailings and retrieve opt-out records through the API to update your own contact lists.\nOptional unsubscribe footer\nRecipient-specific opt-out links\nRetrieve unsubscribe records by mailbox\nGET /email/unsubscribed/", "tags": [], "contentHash": "50f5d1264e5fa9d0f062db7f053f2e557b47bb01e061b64e91918f0c9e3a7524", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "feature-automation", "title": "Make email part of your workflow", "category": "features", "language": "en", "url": "https://mailbridgeapi.com/features/#automation", "summary": "Connect API requests to your business logic. Build automated responses, data extraction, or AI-assisted workflows around your existing mailbox. Integrate from any HTTP-capable tool Connect your own AI workflows Keep control of when messages", "content": "Connect API requests to your business logic. Build automated responses, data extraction, or AI-assisted workflows around your existing mailbox.\nIntegrate from any HTTP-capable tool\nConnect your own AI workflows\nKeep control of when messages are sent\nYOUR LOGIC. YOUR WORKFLOW.", "tags": [], "contentHash": "d5d867caecf01e2fb49f8b6ec98bb0555955ad676a88535058f8f393de4fba6b", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "faq-1", "title": "Do I need to change my email provider?", "category": "faq", "language": "en", "url": "https://mailbridgeapi.com/#main", "summary": "No. MailBridgeAPI connects to an existing mailbox using SMTP for sending and IMAP for reading. Your provider must allow compatible access, and may require an app password or particular security settings.", "content": "No. MailBridgeAPI connects to an existing mailbox using SMTP for sending and IMAP for reading. Your provider must allow compatible access, and may require an app password or particular security settings.", "tags": [ "question" ], "contentHash": "c3da9eef54e797c4d83464168c91f869935122bde471273f432222ebcf40844e", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "faq-2", "title": "What do I need to get started?", "category": "faq", "language": "en", "url": "https://mailbridgeapi.com/#main", "summary": "An account and the connection settings for a mailbox you are authorized to use: SMTP and IMAP hosts, ports, usernames, and credentials. Add these in the dashboard, then use your account API key and mailbox key in your requests.", "content": "An account and the connection settings for a mailbox you are authorized to use: SMTP and IMAP hosts, ports, usernames, and credentials. Add these in the dashboard, then use your account API key and mailbox key in your requests.", "tags": [ "question" ], "contentHash": "e76a9aa642f00506728a105a3131276a3cc3b7962cfbe8ea6c44c4a69e7893c7", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "faq-3", "title": "Can I connect more than one mailbox?", "category": "faq", "language": "en", "url": "https://mailbridgeapi.com/#main", "summary": "Yes. You can configure multiple mailboxes and choose the one to use with the apikeybox parameter. Check your account or contact us for any mailbox limits applicable to your subscription.", "content": "Yes. You can configure multiple mailboxes and choose the one to use with the apikeybox parameter. Check your account or contact us for any mailbox limits applicable to your subscription.", "tags": [ "question" ], "contentHash": "7a05f9ee5f4e9f97878a0b5987e7a60cb9f49cb238b64166519a52f482849303", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "faq-4", "title": "Can a developer integrate my mailbox without knowing its password?", "category": "faq", "language": "en", "url": "https://mailbridgeapi.com/#main", "summary": "Yes. You enter the mailbox’s SMTP and IMAP credentials yourself in the MailBridgeAPI dashboard. Your authorized developer uses your account API key and mailbox key in the project’s backend. They do not need your mailbox password. MailBridge", "content": "Yes. You enter the mailbox’s SMTP and IMAP credentials yourself in the MailBridgeAPI dashboard. Your authorized developer uses your account API key and mailbox key in the project’s backend. They do not need your mailbox password. MailBridgeAPI needs those credentials to connect to your provider, and the API keys must also be kept secret because they allow email operations.", "tags": [ "question" ], "contentHash": "5a5e685a213c2a34796ed5e2e32d3db0edd00fb6050d150c6f510f906364f8c6", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "faq-5", "title": "Can I use MailBridgeAPI with my own business tools or AI workflows?", "category": "faq", "language": "en", "url": "https://mailbridgeapi.com/#main", "summary": "Yes. Any backend or automation tool that can make HTTP requests can use the documented endpoints. Your application supplies the workflow logic, scheduling, customer matching, and any AI processing. These are integrations you build, rather t", "content": "Yes. Any backend or automation tool that can make HTTP requests can use the documented endpoints. Your application supplies the workflow logic, scheduling, customer matching, and any AI processing. These are integrations you build, rather than preconfigured applications included with the API.", "tags": [ "question" ], "contentHash": "005109971a2e1fe31273a3726af04eb455124c5702878b680fdbef8ad65e32ea", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "faq-6", "title": "Are email API requests unlimited?", "category": "faq", "language": "en", "url": "https://mailbridgeapi.com/#main", "summary": "Both published plans include unlimited email API requests. Individual endpoints have rate limits, and your email provider’s sending limits and acceptable-use rules still apply.", "content": "Both published plans include unlimited email API requests. Individual endpoints have rate limits, and your email provider’s sending limits and acceptable-use rules still apply.", "tags": [ "question" ], "contentHash": "68015fc437e3ff936dd7ccc8618da26e01f45bdb609a56a6f0e95f1abb4967ae", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "faq-7", "title": "How does the free trial work?", "category": "faq", "language": "en", "url": "https://mailbridgeapi.com/#main", "summary": "You can try MailBridgeAPI for 3 days without a credit card. Choose monthly or annual billing when you are ready to continue.", "content": "You can try MailBridgeAPI for 3 days without a credit card. Choose monthly or annual billing when you are ready to continue.", "tags": [ "question" ], "contentHash": "a0e8dfcc735cea0711e5db92a1f27d1cb5ce785ceb3cf3095d7ff8f45c75bbf6", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-multiple-projects", "title": "Connect one mailbox to several projects.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#multiple-projects", "summary": "DEVELOPMENT TEAMS Use the same mailbox across internal tools and applications while managing its connection settings centrally. Scenario: A website, an invoicing tool, and an operations script all use the same mailbox. A provider setting ch", "content": "DEVELOPMENT TEAMS\nUse the same mailbox across internal tools and applications while managing its connection settings centrally.\nScenario: A website, an invoicing tool, and an operations script all use the same mailbox. A provider setting changes.\n1. Configure the mailbox’s SMTP and IMAP access in MailBridgeAPI.\n2. Your authorized projects use the account and mailbox keys for their requests.\n3. Update the mailbox connection in the dashboard when its provider settings change.\nBenefit: Mailbox configuration lives in one place. You avoid distributing the mailbox password across each project.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "DEVELOPMENT TEAMS", "multiple-projects" ], "contentHash": "d149400a0f168b20d5b0c527bc1bdbbf50c92203453247721b9bc45cfd8074f8", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-agencies", "title": "Build for clients without asking for their email password.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#agencies", "summary": "AGENCIES & FREELANCERS Connect a client’s mailbox to their website or application using API keys. The client handles the mailbox credentials. Scenario: A client wants their website to send enquiry acknowledgements from contact@theircompany.", "content": "AGENCIES & FREELANCERS\nConnect a client’s mailbox to their website or application using API keys. The client handles the mailbox credentials.\nScenario: A client wants their website to send enquiry acknowledgements from contact@theircompany.com, but does not want to share the mailbox password with the development team.\n1. The client enters their SMTP and IMAP settings in the MailBridgeAPI dashboard.\n2. They provide the account API key and the key for the mailbox to the authorized developer.\n3. The developer keeps those keys in the project’s server configuration and sends acknowledgements through the API.\nBenefit: A clearer handoff: the client manages the mailbox connection, while the developer works with API access.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "AGENCIES & FREELANCERS", "agencies" ], "contentHash": "554734be04995e931857a85fd93d963475903ea37dd4391e237fffc135084026", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-support", "title": "Put email conversations where your team works.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#support", "summary": "CUSTOMER SUPPORT Read customer messages inside your support tool and send replies from your existing support address. Scenario: Your team switches between a shared inbox and an internal support application to handle the same customer reques", "content": "CUSTOMER SUPPORT\nRead customer messages inside your support tool and send replies from your existing support address.\nScenario: Your team switches between a shared inbox and an internal support application to handle the same customer requests.\n1. Your application fetches messages from the support mailbox’s INBOX.\n2. It associates messages with customer records or tickets using your own matching rules.\n3. An agent writes a response in your tool; your backend sends it through the connected mailbox.\nBenefit: Less switching between tools and a customer conversation attached to the work it belongs to.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "CUSTOMER SUPPORT", "support" ], "contentHash": "ac46fea0b2e4348868347ee143782c48944640900de419b23aae67ba96875ff8", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-invoices", "title": "Send invoices from the address customers recognize.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#invoices", "summary": "FINANCE & OPERATIONS Deliver invoices, payment instructions, and follow-ups from your accounting workflow. Scenario: An invoice is ready in your internal system. Someone still downloads the PDF, opens an email client, and attaches it by han", "content": "FINANCE & OPERATIONS\nDeliver invoices, payment instructions, and follow-ups from your accounting workflow.\nScenario: An invoice is ready in your internal system. Someone still downloads the PDF, opens an email client, and attaches it by hand.\n1. Your application generates the invoice and prepares the recipient and message.\n2. It encodes the PDF attachment and calls the sending endpoint.\n3. It checks the API’s SMTP result and records that result against the invoice.\nBenefit: Fewer manual steps, consistent email content, and a recognizable sender for your customers.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "FINANCE & OPERATIONS", "invoices" ], "contentHash": "6294e8c845c675a686fe84fda287cd19f726a841c537dff4a67917532b399410", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-commerce", "title": "Keep customers informed as an order moves forward.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#commerce", "summary": "E-COMMERCE & BOOKINGS Send order updates, appointment details, and booking confirmations from your own business mailbox. Scenario: A booking is confirmed or an order changes status in your application. The customer needs the right details a", "content": "E-COMMERCE & BOOKINGS\nSend order updates, appointment details, and booking confirmations from your own business mailbox.\nScenario: A booking is confirmed or an order changes status in your application. The customer needs the right details at the right moment.\n1. Your application detects the order or booking event.\n2. It prepares an email using the customer’s details and the event information.\n3. Your backend sends the message through MailBridgeAPI and checks the send result.\nBenefit: Communication follows the business event, using the email identity your customer already knows.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "E-COMMERCE & BOOKINGS", "commerce" ], "contentHash": "f655159bf666dcc2293f307de5da611e1f97069cac4519cd9457d0023481272e", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-ai", "title": "Turn incoming emails into useful input for your AI tools.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#ai", "summary": "AI-ASSISTED WORK Build email classification, request summaries, and reply drafts around a connected mailbox. Scenario: Your team receives repetitive enquiries and wants help identifying the topic and preparing a first draft. 1. Your backend", "content": "AI-ASSISTED WORK\nBuild email classification, request summaries, and reply drafts around a connected mailbox.\nScenario: Your team receives repetitive enquiries and wants help identifying the topic and preparing a first draft.\n1. Your backend retrieves the relevant messages through the IMAP endpoint.\n2. Your chosen AI service summarizes or classifies the content according to your rules.\n3. Your team reviews a draft before your application sends the approved response.\nBenefit: A practical route from inbox content to assisted work, with human review where you need it.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "AI-ASSISTED WORK", "ai" ], "contentHash": "38c5c9f5a05d9f6f747336caf5227b14c40149a5889d3f98d6a0127520257cf9", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-automations", "title": "Make email a step in your existing workflow.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#automations", "summary": "AUTOMATION & INTERNAL TOOLS Connect an HTTP-capable automation tool to your mailbox for notifications and scheduled processing. Scenario: An approved request in your business system should trigger an email, or a scheduled workflow needs to ", "content": "AUTOMATION & INTERNAL TOOLS\nConnect an HTTP-capable automation tool to your mailbox for notifications and scheduled processing.\nScenario: An approved request in your business system should trigger an email, or a scheduled workflow needs to collect new inbox messages.\n1. Configure a scheduled job or an event in your application or automation tool.\n2. Use its HTTP request step with your account and mailbox keys.\n3. Process the JSON response and decide what the next step should do.\nBenefit: Email becomes part of the process instead of a separate task someone has to remember.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "AUTOMATION & INTERNAL TOOLS", "automations" ], "contentHash": "cc41f893a24f23a2e89e80e12ebb64eb5f062b4bc8c84044d0181b4371c9e474", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "use-case-contact-lists", "title": "Keep opt-out records connected to your contact list.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/#contact-lists", "summary": "CUSTOMER COMMUNICATION Retrieve unsubscribe records and use them to update the mailing list in your own application. Scenario: Your application sends customer communications and needs to respect recipients who have asked to opt out. 1. Conf", "content": "CUSTOMER COMMUNICATION\nRetrieve unsubscribe records and use them to update the mailing list in your own application.\nScenario: Your application sends customer communications and needs to respect recipients who have asked to opt out.\n1. Configure the unsubscribe footer and enable it on the relevant sends.\n2. Retrieve unsubscribe records for the mailbox through the API.\n3. Match those recipients to your contact list and exclude them from future applicable mailings.\nBenefit: Opt-out information becomes part of your list-management workflow, instead of a disconnected record.\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.", "tags": [ "CUSTOMER COMMUNICATION", "contact-lists" ], "contentHash": "c41449920febf4379b20c5a389d339a1878d4949349d1b7f4e42a0d913c32592", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "audiences", "title": "One connection. Value at every level.", "category": "use-cases", "language": "en", "url": "https://mailbridgeapi.com/use-cases/", "summary": "For mailbox owners Keep your familiar address and enter your connection settings yourself. A developer can integrate your mailbox without asking for its password. For developers and agencies Use account and mailbox API keys in your backend.", "content": "For mailbox owners\nKeep your familiar address and enter your connection settings yourself. A developer can integrate your mailbox without asking for its password.\nFor developers and agencies\nUse account and mailbox API keys in your backend. Reuse the same HTTP integration pattern across client projects.\nFor business teams\nBring emails into the tools you already work in, and send updates from the address your customers recognize.", "tags": [], "contentHash": "82bd1066c0ffecd0ffaaa3a3454de7ea3356bb2d16e6012b732d48c26dc39604", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "api-authentication", "title": "Authentication", "category": "api", "language": "en", "url": "https://mailbridgeapi.com/doc/#authentication", "summary": "Requests require two values: apikey identifies your account; apikeybox selects a configured mailbox. Examples use the documented request parameters. Keep keys in server-side environment variables. For GET endpoints, query parameters can app", "content": "Requests require two values: apikey identifies your account; apikeybox selects a configured mailbox. Examples use the documented request parameters. Keep keys in server-side environment variables.\nFor GET endpoints, query parameters can appear in logs. The published reference also describes Bearer authentication for the account key; verify support in your integration before adopting it.\nIdentifies your account. Find it in your MailBridgeAPI dashboard.\nSelects the mailbox to send from or read. This is the apikeybox value in your dashboard.\nMailBridgeAPI still needs the owner’s mailbox credentials to connect to the email provider. API keys grant access to email operations: treat them as secrets and keep them in your backend.", "tags": [ "apikey", "apikeybox", "authentication" ], "contentHash": "1109ea037745fb933ec33617d7191fee12fd9b89741af443256f291cda085862", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "api-send", "title": "Send an email", "category": "api", "language": "en", "url": "https://mailbridgeapi.com/doc/#send", "summary": "POST https://api.mailbridgeapi.com/sendemail/ Send an email through the SMTP connection of the selected mailbox. Supports HTML, text, CC recipients, attachments, inline images, and an optional unsubscribe footer. Parameters: apikey (Require", "content": "POST https://api.mailbridgeapi.com/sendemail/\nSend an email through the SMTP connection of the selected mailbox. Supports HTML, text, CC recipients, attachments, inline images, and an optional unsubscribe footer.\nParameters:\napikey (Required): Account API key.\napikeybox (Required): API key of the SMTP mailbox to use.\nrecipient_email (Required): Primary recipient email address.\nmail_subject (Required): Email subject.\nmail_body (Required): HTML or plain text message body.\nsender_email (Optional): Override the sender address; defaults to the SMTP mailbox sender. Your provider must allow the address.\nsender_name (Optional): Override the sender display name.\nreply_email (Optional): Reply-To address; defaults to sender_email.\nreply_name (Optional): Reply-To display name.\nemail_cc1, email_cc2, email_cc3 (Optional): Up to three CC recipients.\nformat (Optional): html (default) or text.\ncharset (Optional): Message character set; defaults to UTF-8.\nattachmentBase64_1, attachmentBase64_2 (Optional): Attachment contents encoded as base64.\nattachmentBase64_name_1, attachmentBase64_name_2 (Optional): Filenames for the corresponding attachments.\nembeddedImage (Optional): Public image URL to embed inline.\nembeddedImage_cid (Optional): Content ID referenced in HTML using cid:YOUR_CID.\nunsubscribe (Optional): Set to 1 to append the configured unsubscribe footer; default 0.\nfrom_source (Optional): An optional source label for your send.\nallow_self_signed (Optional): Set to yes to allow self-signed TLS certificates. Omit for normal certificate validation.\nExample response (illustrative, not live mailbox data):\n{\n \"result\": {\n \"error\": \"0\",\n \"sent\": \"OK\",\n \"id\": \"msg_example\"\n }\n}\nCheck result.error = \"0\" and result.sent = \"OK\". The SMTP server accepted the send; this does not guarantee delivery to the recipient’s inbox.\nPublished limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.", "tags": [ "send", "/sendemail/", "SMTP" ], "contentHash": "8838967e1ab8f461bd12d8ccbd9019f72ede5ddf6066680d231c3ec507bb4914", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "api-receive", "title": "Retrieve emails", "category": "api", "language": "en", "url": "https://mailbridgeapi.com/doc/#receive", "summary": "GET https://api.mailbridgeapi.com/getemail/ Read messages from a selected IMAP folder. The result contains a UID-keyed map under result.emaillist. Each page contains up to 30 messages; increment start by 30 to retrieve the next page. Parame", "content": "GET https://api.mailbridgeapi.com/getemail/\nRead messages from a selected IMAP folder. The result contains a UID-keyed map under result.emaillist. Each page contains up to 30 messages; increment start by 30 to retrieve the next page.\nParameters:\napikey (Required): Account API key.\napikeybox (Required): API key of the connected IMAP mailbox.\nmbox (Required): IMAP folder name, such as INBOX, Sent, or Drafts.\nstart (Optional): Zero-based index; defaults to 0. Up to 30 messages per page.\nExample response (illustrative, not live mailbox data):\n{\n \"result\": {\n \"error\": \"0\",\n \"emaillist\": {\n \"50123\": {\n \"id\": 50123,\n \"object\": \"Hello%20there\",\n \"body\": \"%3Cp%3EHello%3C%2Fp%3E\",\n \"email1\": \"jane@example.com\",\n \"email2\": \"hello@yourcompany.com\",\n \"timestamp\": 1736505600,\n \"date\": \"10/01/2025 - 09:20:00\",\n \"size\": 42,\n \"attachment\": null,\n \"loop\": 0\n }\n }\n }\n}\nMessages are grouped by their IMAP UID under result.emaillist. Subject (object) and body may be URL-encoded. Decode those fields before displaying them as text.\nPublished limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.", "tags": [ "receive", "/getemail/", "IMAP" ], "contentHash": "97741a53784847d423b5a363ec9a790e935c54077224c545b815f5054df4431f", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "api-unsubscribe", "title": "Unsubscribe records", "category": "api", "language": "en", "url": "https://mailbridgeapi.com/doc/#unsubscribe", "summary": "GET https://api.mailbridgeapi.com/email/unsubscribed/ Retrieve up to 500 unsubscribe-related send records for a mailbox under result.customer. Optionally filter by recipient email. The start parameter is reserved and may be ignored. Paramet", "content": "GET https://api.mailbridgeapi.com/email/unsubscribed/\nRetrieve up to 500 unsubscribe-related send records for a mailbox under result.customer. Optionally filter by recipient email. The start parameter is reserved and may be ignored.\nParameters:\napikey (Required): Account API key.\napikeybox (Required): API key of the SMTP mailbox.\nemail (Optional): Filter records by recipient email address.\nstart (Optional): Reserved index; may be ignored by the current implementation.\nExample response (illustrative, not live mailbox data):\n{\n \"result\": {\n \"error\": \"0\",\n \"customer\": [\n {\n \"recipientEmail\": \"jane@example.com\",\n \"subject\": \"Monthly update\",\n \"unsubscribeaskedDate\": \"2025-01-11\"\n }\n ]\n }\n}\nRecords are under result.customer. Use recipientEmail to update your list. This endpoint reads opt-out records; it does not unsubscribe a contact itself.\nPublished limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.", "tags": [ "unsubscribe", "/email/unsubscribed/", "unsubscribe" ], "contentHash": "c02504da08924afb112b6a1990ab23da79cd75a6a387a576a91fa0abfe2a4be5", "updatedAt": "2026-09-04T16:41:42.524Z" }, { "id": "api-errors", "title": "API responses, errors and troubleshooting", "category": "api", "language": "en", "url": "https://mailbridgeapi.com/doc/#errors", "summary": "A 200 HTTP response alone does not mean the email was sent. Inspect result.error and result.sent before treating an SMTP request as successful. 200: Request processed. Inspect result.error for the provider result. 400: Required parameters a", "content": "A 200 HTTP response alone does not mean the email was sent. Inspect result.error and result.sent before treating an SMTP request as successful.\n200: Request processed. Inspect result.error for the provider result.\n400: Required parameters are missing.\n401: Invalid or expired API key, or a deactivated account.\n500: SMTP / IMAP provider failure or an internal error.\n401 / invalid key: Check both keys, the selected mailbox, and the account’s active status.\nSMTP connection failure: Check SMTP host, port, authentication, and sender permissions in the dashboard.\nIMAP connection failure: Check IMAP access, credentials, and the exact folder name.\nNo messages returned: Try INBOX with start = 0. The folder may be empty.\nTimeout after sending: Check your dashboard or Sent folder before retrying. The send may already have happened.\nThe send result is unknown. Check the mailbox or dashboard before trying again to avoid sending a duplicate.", "tags": [ "errors", "timeout", "SMTP", "IMAP" ], "contentHash": "cab1f312b01322146a7719a2d0928e781e0c8ecdd49e61b2f6a2e802f1af1860", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "api-explorer", "title": "Try the API with your mailbox", "category": "api", "language": "en", "url": "https://mailbridgeapi.com/doc/#api-connection", "summary": "Connect your account key, choose a mailbox, then run a request below. These requests use the live MailBridgeAPI service. Your key is ready to use. The API checks it when you run your first request. Keys stay in this page’s memory and are cl", "content": "Connect your account key, choose a mailbox, then run a request below. These requests use the live MailBridgeAPI service.\nYour key is ready to use. The API checks it when you run your first request.\nKeys stay in this page’s memory and are cleared on disconnect or reload. Requests pass through this website’s server to MailBridgeAPI.\nThis is a live send, not a simulation. Your provider’s sending limits apply.\nI understand this sends a real email to the recipient entered above.\nThe explorer accepts up to 1 MB per request. Keep test attachments small.\nThe response is displayed as text. Email HTML and attachments are never executed.", "tags": [ "test", "connect", "playground" ], "contentHash": "6484503753fa874a7dff86e116a260ba146b61db87ce40ab88edbd78e7f610e9", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "company-and-contact", "title": "Company and contact", "category": "company", "language": "en", "url": "https://mailbridgeapi.com/about-us/", "summary": "MailBridgeAPI is a service by APPHUBIC LTD. 20 Wenlock Road, London, England, N1 7GU Company number 16438256 For product questions, account help, and integration support. info@mailbridgeapi.com", "content": "MailBridgeAPI is a service by APPHUBIC LTD.\n20 Wenlock Road, London, England, N1 7GU\nCompany number 16438256\nFor product questions, account help, and integration support.\ninfo@mailbridgeapi.com", "tags": [], "contentHash": "82d9b9f243e0d581d759647fbc75d9b562f04afcd949153c184ed5a50e7752e7", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "create-account", "title": "Create your MailBridgeAPI account", "category": "getting-started", "language": "en", "url": "https://mailbridgeapi.com/signup/", "summary": "Create your secure workspace, connect a mailbox, and use its API key in every project. No credit card is required for the trial. You will receive an account ID and licence after registration. Your SMTP and IMAP passwords stay in the dashboa", "content": "Create your secure workspace, connect a mailbox, and use its API key in every project. No credit card is required for the trial.\nYou will receive an account ID and licence after registration.\nYour SMTP and IMAP passwords stay in the dashboard.\nProjects use a revocable API key instead of mailbox credentials.\nChange a mailbox password once without updating every integration.\n3-day trial · No credit card · Cancel anytime", "tags": [ "signup", "account", "trial", "credentials" ], "contentHash": "7789537f5d5dfd3e4b5341bc34c498be8ecbf0d4a31352c8c2a807406fa40591", "updatedAt": "2026-09-04T19:56:04.468Z" }, { "id": "account-sign-in", "title": "Sign in to your MailBridgeAPI account", "category": "getting-started", "language": "en", "url": "https://mailbridgeapi.com/connect/", "summary": "Use your account ID and licence to open the dashboard and manage mailboxes, API keys, email activity, and automations. Enter the credentials provided when your account was created. Manage SMTP and IMAP connections centrally. Keep mailbox pa", "content": "Use your account ID and licence to open the dashboard and manage mailboxes, API keys, email activity, and automations.\nEnter the credentials provided when your account was created.\nManage SMTP and IMAP connections centrally.\nKeep mailbox passwords out of projects and repositories.\nReview email activity and ChatGPT mailbox settings.\nEncrypted connection · Private dashboard · Central access", "tags": [ "connect", "login", "account ID", "licence", "dashboard" ], "contentHash": "190f421b30bf1a462004120b127e59886056cb67f76a3d6042e649902650f20e", "updatedAt": "2026-09-04T19:56:04.468Z" }, { "id": "mailbox-to-api", "title": "Turn a standard email mailbox into an API.", "category": "product", "language": "en", "url": "https://mailbridgeapi.com/#mailbox-to-api", "summary": "Connect SMTP and IMAP once. MailBridgeAPI gives your applications HTTP endpoints to trigger actions with that mailbox, while you keep your existing address and provider. POST /sendemail/ Send email Trigger an API request to send from your c", "content": "Connect SMTP and IMAP once. MailBridgeAPI gives your applications HTTP endpoints to trigger actions with that mailbox, while you keep your existing address and provider.\nPOST /sendemail/\nSend email\nTrigger an API request to send from your connected address.\nGET /getemail/\nRetrieve email\nRead messages from the connected mailbox through a JSON response.\nGET /email/unsubscribed/\nSync unsubscribes\nRetrieve opt-out records for your own contact workflows.", "tags": [ "mailbox", "email API", "endpoint", "HTTP", "SMTP", "IMAP" ], "contentHash": "b899d5dff7e2c76fe32655b382aa052f9141e754ce1d9d627fa14aa0a10afd23", "updatedAt": "2026-09-04T20:08:42.357Z" }, { "id": "smsmobileapi-overview", "title": "Turn your mobile phone into an SMS and call API.", "category": "ecosystem", "language": "en", "url": "https://mailbridgeapi.com/smsmobileapi/", "summary": "SMSMobileAPI connects a mobile phone to your applications through a REST API. Send SMS through the connected phone, retrieve received messages, and bring missed, incoming, and outgoing call activity into your workflows. SMS and call operati", "content": "SMSMobileAPI connects a mobile phone to your applications through a REST API. Send SMS through the connected phone, retrieve received messages, and bring missed, incoming, and outgoing call activity into your workflows.\nSMS and call operations pass through the SMSMobileAPI mobile app installed on the connected phone.\nConnect real mobile activity to the tools you already use.\nUse the phone and mobile number that belong to your workflow. The app creates the bridge between the device, the SMSMobileAPI dashboard, and your software.\nSend SMS through an API\nTrigger an API request and let the connected phone send the message through its mobile service.\nRetrieve received SMS\nBring incoming SMS into a CRM, support tool, automation, or your own application.\nRetrieve call activity\nAccess synchronized missed calls, answered incoming calls, and outgoing calls through documented endpoints.\nBuild with your own phone\nKeep the mobile device and number at the center of the workflow while your applications communicate through an API key.\nA simple bridge in three steps.\nInstall the mobile app\nInstall SMSMobileAPI on the phone that will connect to your workflow.\nConnect the device\nLink the phone to your account and obtain the API credentials used by your backend.\nCall the endpoints\nSend SMS or retrieve SMS and supported call activity from your application.\nEmail for one project. Mobile communication for the next.\nMailBridgeAPI: Connect an existing SMTP and IMAP mailbox to endpoints for sending and retrieving email.\nSMSMobileAPI: Connect a mobile phone to endpoints for SMS and synchronized mobile call activity.\nFeature availability and synchronization depend on the connected device, operating-system permissions, network access, and the installed app version. Call synchronization is documented for the Android app.", "tags": [ "SMSMobileAPI", "SMS API", "mobile phone", "missed calls", "incoming calls", "outgoing calls", "APPHUBIC LTD" ], "contentHash": "cf17839f0c723892311a56f5ba0c46315ce57760bc57429aad497992f5e26d8d", "updatedAt": "2026-09-05T16:05:28.291Z" }, { "id": "service-policy-status", "title": "Service policy questions", "category": "policies", "language": "en", "url": "https://mailbridgeapi.com/terms-and-conditions-of-sale/", "summary": "The published legacy legal texts require review. Do not infer refund, cancellation, retention, encryption or compliance guarantees from this knowledge base. Refer questions about service policies to info@mailbridgeapi.com and the linked pol", "content": "The published legacy legal texts require review. Do not infer refund, cancellation, retention, encryption or compliance guarantees from this knowledge base. Refer questions about service policies to info@mailbridgeapi.com and the linked policy pages.", "tags": [], "contentHash": "f968770fb45565183e06155c7a04d0f5f4c0d932d53518d50fdfa8dd74d9d3b7", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "reference-use-cases-credentialRotation", "title": "credentialRotation", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/doc/", "summary": "ONE MAILBOX. EVERY PROJECT. Change the mailbox password once. Keep every project running. Imagine that the same SMTP mailbox sends email from a website, an invoicing tool, internal automations and dozens more projects. When its password or ", "content": "ONE MAILBOX. EVERY PROJECT.\nChange the mailbox password once. Keep every project running.\nImagine that the same SMTP mailbox sends email from a website, an invoicing tool, internal automations and dozens more projects. When its password or provider settings change, update the connection once in MailBridgeAPI.\nWithout MailBridgeAPI\nEvery project stores the SMTP configuration. A password change becomes a search through every application, followed by new deployments and the risk of forgetting one.\nWith MailBridgeAPI\nEvery project calls the same email API. Update the mailbox connection in the dashboard; the applications keep using their existing API integration.\nMailbox settings\nUpdate SMTP / IMAP once\nWebsite\nBilling app\nAutomation\nOne change instead of one change per project.\nWhether the mailbox is used by three projects or hundreds, no source-code or deployment change is needed when only its mailbox password or connection settings change.\nGive projects API access, never the mailbox password.\nDevelopers, other teams and applications work with account and mailbox API keys. The SMTP/IMAP password remains in the MailBridgeAPI dashboard and does not need to be copied into those projects.\nAPI keys can access email operations. Keep them in server-side environment variables or a secret manager; never expose them in a public repository or browser code.", "tags": [], "contentHash": "c6428913990019f1e1a67332bdcfa2612d6fffc00ad5d16b9370916bd5281cd7", "updatedAt": "2026-09-04T18:07:03.910Z" }, { "id": "reference-pricing", "title": "Complete pricing reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/pricing/", "summary": "Simple pricing for your email API. ONE SERVICE. EVERYTHING YOU NEED. All the core tools to connect your mailbox to your application. No per-request pricing to calculate. MailBridgeAPI Your complete email-to-API toolkit. Billed monthly. $9 U", "content": "Simple pricing for your email API.\nONE SERVICE. EVERYTHING YOU NEED.\nAll the core tools to connect your mailbox to your application. No per-request pricing to calculate.\nMailBridgeAPI\nYour complete email-to-API toolkit.\nBilled monthly. $9 USD per month.\n$90 USD billed annually. Equivalent to $7.50 per month.\nFull access to MailBridgeAPI\nUnlimited email API requests\nSMTP sending and IMAP retrieval\nDashboard and API key management\nHeaders, footers, and unsubscribe tools\nPriority support\nEndpoint rate limits and your email provider’s sending policies apply.\nEverything you need, in either plan.\nFeature\nIncluded\n3-day free trial · No credit card required\nYour pricing questions, answered.\nTwo months free compared with monthly billing.", "tags": [], "contentHash": "47628b0c95e97f679103a9e2ae546d4fba1cd384350174e10d40e654d8a00f30", "updatedAt": "2026-09-04T17:46:19.414Z" }, { "id": "reference-product", "title": "Complete product reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/services/", "summary": "MEET YOUR EMAIL’S NEW SUPERPOWER. Connect your mailbox to an email API. MailBridgeAPI turns your existing SMTP and IMAP mailbox into an email API. Connect once, then call HTTP endpoints to send and retrieve emails across your projects. Keep", "content": "MEET YOUR EMAIL’S NEW SUPERPOWER.\nConnect your mailbox to an email API.\nMailBridgeAPI turns your existing SMTP and IMAP mailbox into an email API. Connect once, then call HTTP endpoints to send and retrieve emails across your projects.\nKeep the mailbox. Simplify the integration.\nSMTP and IMAP are how email works. You shouldn’t have to rebuild that connection in every project. MailBridgeAPI gives your applications a consistent API while you manage your mailbox settings in one dashboard.\nYour mailbox stays yours.\nMailBridgeAPI uses your existing email service. It does not replace your email provider or remove its limits. You keep your address and continue using your usual email client.\nWhat you’ll need\nA mailbox you are authorized to connect\nSMTP host, port, username, and credentials\nIMAP host, port, username, and credentials\nProvider-approved authentication and access settings\nOne mailbox, multiple projects. Update its connection settings in one place.", "tags": [], "contentHash": "63f554c22d444cd7084122c5360c565826ca8a0179618df44d91ab00f63de522", "updatedAt": "2026-09-04T20:04:49.808Z" }, { "id": "reference-features", "title": "Complete features reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/features/", "summary": "Send from your own address Send transactional emails and notifications through your connected SMTP mailbox. Your provider and sender identity stay with you. HTML or plain text messages Custom sender and reply-to names CC recipients and base", "content": "Send from your own address\nSend transactional emails and notifications through your connected SMTP mailbox. Your provider and sender identity stay with you.\nHTML or plain text messages\nCustom sender and reply-to names\nCC recipients and base64 attachments\nPOST /sendemail/\nBring your inbox into your app\nRetrieve incoming messages from your IMAP folders. Turn customer requests, alerts, and replies into useful application data.\nSelect an IMAP folder\nRetrieve up to 30 messages per page\nWork with a JSON response\nGET /getemail\nIntegrate without the mailbox password\nThe mailbox owner enters their credentials in MailBridgeAPI. Your developer uses API keys to connect the project, without needing to know the email password.\nThe owner configures the mailbox connection\nYour backend uses account and mailbox keys\nMailbox passwords stay out of project code\napikey + apikeybox\nConsistent emails, by default\nConfigure a shared header and footer in the dashboard. Keep your branding and signature consistent across the emails your applications send.\nReusable headers and footers\nCompany signatures and disclaimers\nUpdate content from your dashboard\nCONFIGURE ONCE\nKeep your contact lists in sync\nEnable unsubscribe links for your mailings and retrieve opt-out records through the API to update your own contact lists.\nOptional unsubscribe footer\nRecipient-specific opt-out links\nRetrieve unsubscribe records by mailbox\nGET /email/unsubscribed/\nMake email part of your workflow\nConnect API requests to your business logic. Build automated responses, data extraction, or AI-assisted workflows around your existing mailbox.\nIntegrate from any HTTP-capable tool\nConnect your own AI workflows\nKeep control of when messages are sent\nYOUR LOGIC. YOUR WORKFLOW.", "tags": [], "contentHash": "ae924b26191c6433dfaf9d78687cff22a5d3b46d28260c96f47dd0495fff42dc", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "reference-faq", "title": "Complete faq reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "Do I need to change my email provider? No. MailBridgeAPI connects to an existing mailbox using SMTP for sending and IMAP for reading. Your provider must allow compatible access, and may require an app password or particular security setting", "content": "Do I need to change my email provider?\nNo. MailBridgeAPI connects to an existing mailbox using SMTP for sending and IMAP for reading. Your provider must allow compatible access, and may require an app password or particular security settings.\nWhat do I need to get started?\nAn account and the connection settings for a mailbox you are authorized to use: SMTP and IMAP hosts, ports, usernames, and credentials. Add these in the dashboard, then use your account API key and mailbox key in your requests.\nCan I connect more than one mailbox?\nYes. You can configure multiple mailboxes and choose the one to use with the apikeybox parameter. Check your account or contact us for any mailbox limits applicable to your subscription.\nCan a developer integrate my mailbox without knowing its password?\nYes. You enter the mailbox’s SMTP and IMAP credentials yourself in the MailBridgeAPI dashboard. Your authorized developer uses your account API key and mailbox key in the project’s backend. They do not need your mailbox password. MailBridgeAPI needs those credentials to connect to your provider, and the API keys must also be kept secret because they allow email operations.\nCan I use MailBridgeAPI with my own business tools or AI workflows?\nYes. Any backend or automation tool that can make HTTP requests can use the documented endpoints. Your application supplies the workflow logic, scheduling, customer matching, and any AI processing. These are integrations you build, rather than preconfigured applications included with the API.\nAre email API requests unlimited?\nBoth published plans include unlimited email API requests. Individual endpoints have rate limits, and your email provider’s sending limits and acceptable-use rules still apply.\nHow does the free trial work?\nYou can try MailBridgeAPI for 3 days without a credit card. Choose monthly or annual billing when you are ready to continue.", "tags": [], "contentHash": "8d13eecfb77aa80a51bfcf79ce4355c1bc45ffa74afeaf8492cbf3c9f8699ac4", "updatedAt": "2026-09-04T16:33:27.869Z" }, { "id": "reference-docs", "title": "Complete docs reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/doc/", "summary": "MAILBRIDGEAPI / DOCUMENTATION Email API documentation: SMTP and IMAP. Turn an SMTP and IMAP mailbox into an API. Call HTTP endpoints to send messages, retrieve your inbox, and manage unsubscribe records. Overview Quick start Authentication ", "content": "MAILBRIDGEAPI / DOCUMENTATION\nEmail API documentation: SMTP and IMAP.\nTurn an SMTP and IMAP mailbox into an API. Call HTTP endpoints to send messages, retrieve your inbox, and manage unsubscribe records.\nOverview\nQuick start\nAuthentication\nSend an email\nRetrieve emails\nUnsubscribe records\nResponses & errors\nRate limits\nBase URL\nAPI v1\nBefore your first request\nCreate your account and connect your SMTP / IMAP mailbox in the dashboard.\nCopy your account API key and the API key for your mailbox.\nUse these keys in a request from your server. Keep real keys out of browsers, source control, and public logs.\nRequests require two values: apikey identifies your account; apikeybox selects a configured mailbox. Examples use the documented request parameters. Keep keys in server-side environment variables.\nFor GET endpoints, query parameters can appear in logs. The published reference also describes Bearer authentication for the account key; verify support in your integration before adopting it.\nSend an email through the SMTP connection of the selected mailbox. Supports HTML, text, CC recipients, attachments, inline images, and an optional unsubscribe footer.\nRead messages from a selected IMAP folder. The result contains a UID-keyed map under result.emaillist. Each page contains up to 30 messages; increment start by 30 to retrieve the next page.\nRetrieve up to 500 unsubscribe-related send records for a mailbox under result.customer. Optionally filter by recipient email. The start parameter is reserved and may be ignored.\nParameter\nRequired\nOptional\nDescription\nRequest example\nExample response\nA 200 HTTP response alone does not mean the email was sent. Inspect result.error and result.sent before treating an SMTP request as successful.\n200\nRequest processed. Inspect result.error for the provider result.\n400\nRequired parameters are missing.\n401\nInvalid or expired API key, or a deactivated account.\n500\nSMTP / IMAP provider failure or an internal error.\nPublished limits: sending and unsubscribe retrieval — 120 requests/minute; IMAP retrieval — 60 requests/minute. Your provider’s own limits also apply. Handle failures and avoid retrying sends blindly, which can create duplicate emails.\nExamples follow the published MailBridgeAPI v1 reference. Code samples are illustrative; the interactive explorer sends live requests only when you run a test.\nCopy base URL", "tags": [], "contentHash": "14adf268a19f26bdb8ec1a07bc19a155ff47ad679e3ee07c9bfc311dfe3c621f", "updatedAt": "2026-09-04T20:04:49.808Z" }, { "id": "reference-about", "title": "Complete about reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/about-us/", "summary": "A MORE USEFUL CONNECTION. About MailBridgeAPI. MailBridgeAPI helps developers and businesses turn existing email accounts into programmable tools. Email is already part of your business. The next step is making it part of your applications.", "content": "A MORE USEFUL CONNECTION.\nAbout MailBridgeAPI.\nMailBridgeAPI helps developers and businesses turn existing email accounts into programmable tools.\nEmail is already part of your business.\nThe next step is making it part of your applications. Our approach is simple: keep the mailbox you trust, connect its SMTP and IMAP settings once, and give your projects a consistent API to work with.\nBuilt for people who build.\nFrom a small internal script to a customer-facing application, the goal is the same: less repeated email configuration, clearer integrations, and more time to work on the parts that make your product useful.\nThe company behind the bridge\nMailBridgeAPI is a service by APPHUBIC LTD.\n20 Wenlock Road, London, England, N1 7GU\nCompany number 16438256", "tags": [], "contentHash": "016d349d3ef0ec64b3d73575153ee10c7afa3d30aa611beb1360efb8a19acd49", "updatedAt": "2026-09-04T17:46:19.414Z" }, { "id": "reference-use-cases", "title": "Complete use cases reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/use-cases/", "summary": "ONE MAILBOX. MANY WAYS TO BUILD. Email API use cases for your business. From a client website to a customer support workflow, connect the email address you already use to the work you need to get done. Real work. Real reasons to connect. Fo", "content": "ONE MAILBOX. MANY WAYS TO BUILD.\nEmail API use cases for your business.\nFrom a client website to a customer support workflow, connect the email address you already use to the work you need to get done.\nReal work. Real reasons to connect.\nFor the person writing the code, the team using the tool, and the client who owns the mailbox.\nExplore all use cases\nSee how it works\nImagine this\nHow you build it\nWhat your team gains\nExplore the endpoint\nThese are workflows you can build with MailBridgeAPI. Your application or automation tool provides the business logic, scheduling, and any AI processing. Mailbox access depends on your provider; its sending limits still apply.\nOne connection. Value at every level.\nFor mailbox owners\nKeep your familiar address and enter your connection settings yourself. A developer can integrate your mailbox without asking for its password.\nFor developers and agencies\nUse account and mailbox API keys in your backend. Reuse the same HTTP integration pattern across client projects.\nFor business teams\nBring emails into the tools you already work in, and send updates from the address your customers recognize.\nDEVELOPMENT TEAMS\nConnect one mailbox to several projects.\nUse the same mailbox across internal tools and applications while managing its connection settings centrally.\nA website, an invoicing tool, and an operations script all use the same mailbox. A provider setting changes.\nConfigure the mailbox’s SMTP and IMAP access in MailBridgeAPI.\nYour authorized projects use the account and mailbox keys for their requests.\nUpdate the mailbox connection in the dashboard when its provider settings change.\nMailbox configuration lives in one place. You avoid distributing the mailbox password across each project.\nsend\nAGENCIES & FREELANCERS\nBuild for clients without asking for their email password.\nConnect a client’s mailbox to their website or application using API keys. The client handles the mailbox credentials.\nA client wants their website to send enquiry acknowledgements from contact@theircompany.com, but does not want to share the mailbox password with the development team.\nThe client enters their SMTP and IMAP settings in the MailBridgeAPI dashboard.\nThey provide the account API key and the key for the mailbox to the authorized developer.\nThe developer keeps those keys in the project’s server configuration and sends acknowledgements through the API.\nA clearer handoff: the client manages the mailbox connection, while the developer works with API access.\nsend\nCUSTOMER SUPPORT\nPut email conversations where your team works.\nRead customer messages inside your support tool and send replies from your existing support address.\nYour team switches between a shared inbox and an internal support application to handle the same customer requests.\nYour application fetches messages from the support mailbox’s INBOX.\nIt associates messages with customer records or tickets using your own matching rules.\nAn agent writes a response in your tool; your backend sends it through the connected mailbox.\nLess switching between tools and a customer conversation attached to the work it belongs to.\nreceive\nFINANCE & OPERATIONS\nSend invoices from the address customers recognize.\nDeliver invoices, payment instructions, and follow-ups from your accounting workflow.\nAn invoice is ready in your internal system. Someone still downloads the PDF, opens an email client, and attaches it by hand.\nYour application generates the invoice and prepares the recipient and message.\nIt encodes the PDF attachment and calls the sending endpoint.\nIt checks the API’s SMTP result and records that result against the invoice.\nFewer manual steps, consistent email content, and a recognizable sender for your customers.\nsend\nE-COMMERCE & BOOKINGS\nKeep customers informed as an order moves forward.\nSend order updates, appointment details, and booking confirmations from your own business mailbox.\nA booking is confirmed or an order changes status in your application. The customer needs the right details at the right moment.\nYour application detects the order or booking event.\nIt prepares an email using the customer’s details and the event information.\nYour backend sends the message through MailBridgeAPI and checks the send result.\nCommunication follows the business event, using the email identity your customer already knows.\nsend\nAI-ASSISTED WORK\nTurn incoming emails into useful input for your AI tools.\nBuild email classification, request summaries, and reply drafts around a connected mailbox.\nYour team receives repetitive enquiries and wants help identifying the topic and preparing a first draft.\nYour backend retrieves the relevant messages through the IMAP endpoint.\nYour chosen AI service summarizes or classifies the content according to your rules.\nYour team reviews a draft before your application sends the approved response.\nA practical route from inbox content to assisted work, with human review where you need it.\nreceive\nAUTOMATION & INTERNAL TOOLS\nMake email a step in your existing workflow.\nConnect an HTTP-capable automation tool to your mailbox for notifications and scheduled processing.\nAn approved request in your business system should trigger an email, or a scheduled workflow needs to collect new inbox messages.\nConfigure a scheduled job or an event in your application or automation tool.\nUse its HTTP request step with your account and mailbox keys.\nProcess the JSON response and decide what the next step should do.\nEmail becomes part of the process instead of a separate task someone has to remember.\nsend\nCUSTOMER COMMUNICATION\nKeep opt-out records connected to your contact list.\nRetrieve unsubscribe records and use them to update the mailing list in your own application.\nYour application sends customer communications and needs to respect recipients who have asked to opt out.\nConfigure the unsubscribe footer and enable it on the relevant sends.\nRetrieve unsubscribe records for the mailbox through the API.\nMatch those recipients to your contact list and exclude them from future applicable mailings.\nOpt-out information becomes part of your list-management workflow, instead of a disconnected record.\nunsubscribe", "tags": [], "contentHash": "7d982cde63d4c31005888b8dda36af969892c7d2c2ece7bef9f8824fceb835c5", "updatedAt": "2026-09-04T18:07:03.910Z" }, { "id": "reference-password-handoff", "title": "Complete password handoff reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/#password-handoff", "summary": "YOUR PROJECT NEEDS EMAIL. NOT THE EMAIL PASSWORD. Integrate the mailbox. Keep its password out of the project. Your client or mailbox owner connects the email account in MailBridgeAPI. You build the integration with API keys, without needin", "content": "YOUR PROJECT NEEDS EMAIL. NOT THE EMAIL PASSWORD.\nIntegrate the mailbox. Keep its password out of the project.\nYour client or mailbox owner connects the email account in MailBridgeAPI. You build the integration with API keys, without needing to know their mailbox password.\nBuild email integrations without asking your client for their mailbox password.\nMailbox owner\nEnters SMTP / IMAP credentials in MailBridgeAPI.\nMailBridgeAPI\nUses the configured connection to communicate with the mailbox.\nDeveloper & application\nUses account and mailbox API keys to send or retrieve emails.\nMAILBOX CREDENTIALS\nAPI KEYS\nThe developer does not need the mailbox password.\nA more reassuring client handoff\nThe owner enters the mailbox credentials. The developer receives the API access needed for the integration.\nFewer places to share a password\nKeep the mailbox password out of project source code, developer messages, and individual application configurations.\nOne place for connection settings\nWhen mailbox settings change, update the connection in the dashboard instead of redistributing the password across projects.\nMailBridgeAPI still needs the owner’s mailbox credentials to connect to the email provider. API keys grant access to email operations: treat them as secrets and keep them in your backend.\nSee the client integration example", "tags": [], "contentHash": "9eb4636b8598c2836e603a76b5f3341b53245e56ba9fc48d1612dd8abd2fb8b5", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-site-livechat", "title": "livechat website reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "AI support chat The website offers an AI assistant powered by OpenAI. It answers product and integration questions using the current MailBridgeAPI knowledge base and links to supporting pages. It cannot access your account or mailbox, or se", "content": "AI support chat\nThe website offers an AI assistant powered by OpenAI. It answers product and integration questions using the current MailBridgeAPI knowledge base and links to supporting pages. It cannot access your account or mailbox, or send email.\nTo start the AI chat, your name and email address are required and stored by MailBridgeAPI with the conversation. Your messages, recent conversation context and selected public documentation are sent to OpenAI to generate replies; your name and email address are not included in that model context. MailBridgeAPI also stores the language, page, browser information, a pseudonymized network identifier, timestamps, selected sources, token usage, errors and estimated costs for support administration. Conversations are retained on the service server until removed by the operator; they are not added to the public knowledge base. Do not share passwords, API keys or private email content. Contact info@mailbridgeapi.com about your data.\nOpening the chat sets a functional HttpOnly cookie, mb_chat, valid for 30 days, to restore your own conversation. Signing into the private webmaster area sets mb_webmaster for up to 8 hours. These cookies are not used for advertising. Clearing cookies removes the browser link to your conversation but does not delete the server history.", "tags": [], "contentHash": "e8c572fe4127abf0bacbd34d02ee86d94fb82078006ded2edaf827e6e85ec850", "updatedAt": "2026-09-04T18:33:50.038Z" }, { "id": "reference-site-featurePage", "title": "featurePage website reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "BUILT AROUND YOUR MAILBOX. Email API features for your daily workflows. The building blocks for email-enabled applications: sending, reading, mailbox access, and consistent communication.", "content": "BUILT AROUND YOUR MAILBOX.\nEmail API features for your daily workflows.\nThe building blocks for email-enabled applications: sending, reading, mailbox access, and consistent communication.", "tags": [], "contentHash": "301249f2662e856fbd38c87df5ad923e0c3f3a590f64095e60cb4bbde22cd11b", "updatedAt": "2026-09-04T17:46:19.414Z" }, { "id": "reference-site-contact", "title": "contact website reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "LET’S CONNECT. Real questions. Human answers. Need help connecting a mailbox, choosing a plan, or finding the right endpoint? Tell us what you’re building. Email our team For product questions, account help, and integration support. Prefer ", "content": "LET’S CONNECT.\nReal questions. Human answers.\nNeed help connecting a mailbox, choosing a plan, or finding the right endpoint? Tell us what you’re building.\nEmail our team\nFor product questions, account help, and integration support.\nPrefer to start with the docs?\nExplore authentication, endpoints, parameters, and working request examples.\nTell us about your project\nYour name\nWork email\nWhat can we help with?\nYour message\nAlex Morgan\nalex@company.com\nTell us what you’re building or where you’re stuck…\nIntegration question\nAccount and billing\nProduct question\nSomething else\nSend message\nYour request is sent directly to our team. You do not need an email application.\nYour request has been received. Reference:\nYour name, email and message are stored privately so our team can handle your request. Do not include passwords or API keys.\nSending…\nWe could not confirm receipt. Please try again; your message has been kept.\nToo many requests. Please try again in an hour.", "tags": [], "contentHash": "9fcf935cadaec1d5b0ddc81145757cb26b3c20fae974975fdfa2cc256143179a", "updatedAt": "2026-09-04T17:36:14.283Z" }, { "id": "reference-site-cta", "title": "cta website reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "YOUR NEXT INTEGRATION STARTS HERE. Build more with the inbox you already have. Turn your mailbox into an API, call your first email endpoint, and give every project a simpler way to send or retrieve messages. Read the documentation", "content": "YOUR NEXT INTEGRATION STARTS HERE.\nBuild more with the inbox you already have.\nTurn your mailbox into an API, call your first email endpoint, and give every project a simpler way to send or retrieve messages.\nRead the documentation", "tags": [], "contentHash": "510c587693216ae02ba651b27646902dadb5c087c432ee1e01c0146b2a01c3e2", "updatedAt": "2026-09-04T20:04:49.808Z" }, { "id": "reference-site-notFound", "title": "notFound website reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "404 / NOT FOUND This connection leads nowhere. The page may have moved. Let’s get you back to the right place.", "content": "404 / NOT FOUND\nThis connection leads nowhere.\nThe page may have moved. Let’s get you back to the right place.", "tags": [], "contentHash": "764b4c5ba24bdb058f2cc7f7b84495a8b9ab7fd602f1e5283440c2180538b085", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-eyebrow", "title": "eyebrow home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "YOUR MAILBOX. NOW PROGRAMMABLE.", "content": "YOUR MAILBOX. NOW PROGRAMMABLE.", "tags": [], "contentHash": "ab2a62057cafc77c60a095eaaffc4c05705310211ed3a5b04713ddf64c452c61", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-title", "title": "title home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "Your email. Your workflow. One simple API.", "content": "Your email.\nYour workflow.\nOne simple API.", "tags": [], "contentHash": "d8f82ba6eb3161cf72d957db15f8ad5ad52dd74432563b0b435334780852ccff", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-description", "title": "description home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "Turn a standard SMTP and IMAP mailbox into an email API. Your applications can call clear HTTP endpoints to send, receive, and automate email from your own address—without sharing the mailbox password with your developer.", "content": "Turn a standard SMTP and IMAP mailbox into an email API. Your applications can call clear HTTP endpoints to send, receive, and automate email from your own address—without sharing the mailbox password with your developer.", "tags": [], "contentHash": "f3278aecfd35d5a7beb7e0a3644424ab0501a04b61b4bfe25bd532a5fcc16c72", "updatedAt": "2026-09-04T20:04:49.808Z" }, { "id": "reference-home-visual", "title": "visual home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "FROM YOUR INBOX TO YOUR APPLICATION Your existing mailbox Connected Secure connection API key your-next-big-idea.js Your mailbox. Connected to your code. Less configuration. More creation.", "content": "FROM YOUR INBOX TO YOUR APPLICATION\nYour existing mailbox\nConnected\nSecure connection\nAPI key\nyour-next-big-idea.js\nYour mailbox. Connected to your code.\nLess configuration.\nMore creation.", "tags": [], "contentHash": "9b5cb908f513d687613878d9c9152ad200bccd088f2e3a2368eb6271c6a81208", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-providers", "title": "providers home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "YOUR PROVIDER. YOUR ADDRESS. YOUR RULES. Requires compatible SMTP and IMAP access. Your provider may require an app password or specific account settings.", "content": "YOUR PROVIDER. YOUR ADDRESS. YOUR RULES.\nRequires compatible SMTP and IMAP access. Your provider may require an app password or specific account settings.", "tags": [], "contentHash": "992e99250d28424de3e7bed13ab8f2435a6fd536cb369c73347a6e7ca4fb142a", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-features", "title": "features home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "A SMALL BRIDGE. A BIG DIFFERENCE. Email integration, without the heavy lifting. Your mailbox already works. MailBridgeAPI turns it into callable endpoints that any HTTP-capable application can use.", "content": "A SMALL BRIDGE. A BIG DIFFERENCE.\nEmail integration, without the heavy lifting.\nYour mailbox already works. MailBridgeAPI turns it into callable endpoints that any HTTP-capable application can use.", "tags": [], "contentHash": "c2ad516f880f531f38e19f21df44365072c8ff4e9f3f15bd79a511f1f645b525", "updatedAt": "2026-09-04T20:04:49.808Z" }, { "id": "reference-home-steps", "title": "steps home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "THREE STEPS. ENDLESS POSSIBILITIES. From inbox to integration. A familiar mailbox on one side. Your next great idea on the other. Connect your mailbox Add your SMTP and IMAP settings in the dashboard. Keep using your existing address and em", "content": "THREE STEPS. ENDLESS POSSIBILITIES.\nFrom inbox to integration.\nA familiar mailbox on one side. Your next great idea on the other.\nConnect your mailbox\nAdd your SMTP and IMAP settings in the dashboard. Keep using your existing address and email provider.\nSMTP + IMAP\nGet your API keys\nUse your account API key and the key for your chosen mailbox. Your application never needs the mailbox password.\nAPI KEY + MAILBOX KEY\nMake your first request\nSend a message, retrieve your inbox, or connect email to the tools and workflows you already use.\nHTTP REQUEST → EMAIL", "tags": [], "contentHash": "43820c604288873bc9e387b1c2134f9c9b15bb8d66f764bff1ab5b52145b4104", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-developer", "title": "developer home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "MADE FOR THE WAY YOU BUILD. A few lines of code. A lot of possibility. Straightforward HTTP requests. Familiar JSON responses. Bring email into your stack without writing another SMTP or IMAP integration. Send text, HTML, and attachments Re", "content": "MADE FOR THE WAY YOU BUILD.\nA few lines of code. A lot of possibility.\nStraightforward HTTP requests. Familiar JSON responses. Bring email into your stack without writing another SMTP or IMAP integration.\nSend text, HTML, and attachments\nRead messages from your IMAP folders\nUse JavaScript, Python, PHP, or any HTTP client", "tags": [], "contentHash": "e1ad556981c64cff575f8987b330c6f2785cfbbb32fac293e2be575e701ace41", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-pricing", "title": "pricing home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "SIMPLE BY DESIGN. Small price. Full possibility. One complete feature set. Choose the billing cycle that works for you.", "content": "SIMPLE BY DESIGN.\nSmall price. Full possibility.\nOne complete feature set. Choose the billing cycle that works for you.", "tags": [], "contentHash": "5753c8aec1fdf2426161fe53f0863232b44d47dd97fb92671374ff90124bb0df", "updatedAt": "2026-09-04T16:37:57.496Z" }, { "id": "reference-home-faqTitle", "title": "faqTitle home reference", "category": "reference", "language": "en", "url": "https://mailbridgeapi.com/", "summary": "A few things you might be wondering.", "content": "A few things you might be wondering.", "tags": [], "contentHash": "db4cd123f058db8a727cc817b20ab362012776c9aa31f67bf139ff6ab0ccbc2a", "updatedAt": "2026-09-04T16:37:57.496Z" } ] }