WordPress email delivery for forms, accounts, and WooCommerce.

Video walkthrough

Review the setup sequence, then use the written steps for the live WordPress change.

1. Prepare EmailDesk and WordPress

In EmailDesk, confirm the customer has API email sender access, a verified From address on an allowed domain, an active website or application API key, and the required sender DNS.

The From email used by WordPress must belong to a domain allowed by that key, for example info@example.com. Use a form visitor's address in Reply-To, not as an unverified From address.

2. Download the API plugin

Download the latest plugin ZIP from EmailDesk:

https://app.emaildesk.bd/api/downloads/wordpress-plugin?v=1.0.3

3. Install in WordPress

Open WordPress Admin, then go to Plugins > Add New > Upload Plugin. Upload emaildesk-api-sender-1.0.3.zip, select Install Now, and activate EmailDesk API Sender.

After activation, open Settings > EmailDesk API Sender.

4. Configure the API settings

Use these values in the plugin settings page:

API endpoint: https://app.emaildesk.bd/api/v1/send
API key: paste the one-time key created in EmailDesk
From email: info@example.com
From name: Your website or company name
Gateway profile name: optional, for example MailChannels
Message type: transactional
Timeout seconds: 20
Failure behavior: keep fallback enabled during first setup

After entering the values, click Save Settings.

5. Send controlled tests

Use the Send Test Email section first. Then test the workflows the site depends on, such as a contact form, password reset, new account, and a WooCommerce order notice when applicable.

Inspect the WordPress response and EmailDesk Outbound History for the sender, SPF, DKIM, DMARC, policy, queue, and provider evidence. If the intended route is working, enable Route WordPress emails through EmailDesk API.

6. Understand fallback behavior

When fallback is enabled and the EmailDesk API attempt fails, the plugin returns control to normal WordPress mail. That can keep a site operational during setup, but the fallback message follows the web server's mail path and may not appear as an EmailDesk API send.

If fallback is disabled, a failed EmailDesk attempt returns failure to WordPress. Decide which behavior is appropriate before live forms, account notices, or store mail depend on the plugin.

7. Example API payload

The plugin sends WordPress mail to EmailDesk in the same API format used by custom apps:

{
  "fromEmail": "info@example.com",
  "fromName": "Example Website",
  "to": ["customer@example.net"],
  "subject": "Your WordPress notification",
  "body": "This email was sent through EmailDesk.",
  "messageType": "transactional",
  "profileName": "MailChannels"
}

8. Troubleshoot common WordPress failures

A test can fail because the API key is wrong, disabled, or belongs to another customer; the From domain is not allowed; sender DNS is incomplete; the account is suspended; a quota or rate limit applies; or the selected gateway refuses the message.

A WordPress HTTP error or timeout can indicate DNS, TLS, firewall, hosting egress, endpoint, or PHP request problems. Plugin conflicts or another mail plugin can also change which transport handles wp_mail(). Enable the plugin debug log only while investigating and do not publish the API key.

A successful EmailDesk queue or provider handoff is evidence of that stage, not a guarantee of final delivery or inbox placement. Review later bounce, complaint, suppression, or delivery evidence when available.