Skip to content
Jooosi
Account
JM Jooosi Mail

MailerSend

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

MailerSend supports API and SMTP delivery. API is the default and uses an API key. SMTP uses the account SMTP username and password. The profile also supports MailerSend webhook events for delivery tracking.

Before you begin#

Have a provider account and credentials for the transport you chose. Copy credentials from the provider’s own console or account settings; never put secret values in documentation. Check the provider’s documentation for account requirements and sender acceptance.

Supported transport and settings#

  • Transport scheme: mailersend+api (default), mailersend+smtp.
  • Required settings: mailersend+api: MailerSend API key (secret). mailersend+smtp: MailerSend SMTP username and SMTP password (secret).
  • Optional settings: There are no additional provider configuration fields for this profile.

Jooosi Mail marks password, token, key, and private-key fields as secrets in the connection form. Enter only the fields shown for the selected scheme.

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select MailerSend in Profile.
  3. Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
  4. Review the sender, routing, and advanced settings for this connection.
  5. Choose Create connection to save it.

For the shared form workflow, see Connect a provider.

Verify delivery#

Follow Send a test email and send to a mailbox you can check. A test sends a real email. Check the mailbox and Jooosi Mail → Logs for the attempt status. For supported webhooks, see the provider note and Provider webhooks guide.

Webhooks#

MailerSend webhooks are supported. Enable Webhooks under Advanced settings, save the connection, and configure the displayed endpoint in MailerSend. If you enter a shared Webhook secret, the adapter checks the request signature against it; without a secret, unsigned requests are accepted. For event setup, see the shared Provider webhooks guide.

Troubleshooting#

  • Confirm that the API token or SMTP credentials match the selected scheme.
  • If signed webhook deliveries fail, make sure the shared secret matches on both sides and check the webhook event log.

Provider reference: https://developers.mailersend.com.