mailbridgeAPI
DEMOLog inConnect a mailbox
Troubleshooting guide

Change an SMTP password across multiple WordPress sites

Centralize one mailbox connection so a provider password change does not require editing every authorized WordPress installation.

Change an SMTP password across multiple WordPress sitesapikey + apikeyboxUpdate mailbox once · keep site API keys

The problem to solve

A successful application handoff does not always prove that the provider accepted or delivered the email. Diagnose every layer in order.

A practical implementation path

Reproduce the failure with a unique test, inspect the MailBridgeAPI or provider response, confirm mailbox health and only then test recipient delivery.

01 — 03

From mailbox to working request

01

Connect the mailbox

Authorize the mailbox or configure its compatible SMTP and IMAP connection in the MailBridgeAPI dashboard.

02

Keep keys in the backend

Store the account API key and mailbox API key in server-side environment variables or a secret manager.

03

Call and verify the endpoint

Run the request, inspect the JSON response and keep the request or message identifier for support.

Update mailbox once · keep site API keys

Copy-ready example

Centralize one mailbox connection so a provider password change does not require editing every authorized WordPress installation.

  • One mailbox connection managed centrally
  • API access without copying the mailbox password into every project
  • Dashboard activity, errors and mailbox health
  • A testable path from code to the real mailbox
wordpress-env.example
# Each WordPress site keeps mailbox-scoped API access.
MAILBRIDGE_ACCOUNT_KEY=account_key_from_dashboard
MAILBRIDGE_MAILBOX_KEY=mailbox_key_for_this_site

# Change SMTP credentials once in the MailBridgeAPI dashboard.
# No SMTP password is copied into this project.

Provider and implementation limits

The plugin handles software that uses wp_mail(). A plugin that bypasses wp_mail() needs its own integration. Provider and DNS configuration still affect delivery.

LIVE SMTP · IMAP · OAUTH DEMO

Test the real connection before you build

The live demo can validate SMTP, IMAP or a supported OAuth provider and issue temporary API keys without creating an account.

Open the live demoCreate an account
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.