Skip to content
Jooosi
Account
JM Jooosi Mail

ZeptoMail

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

The ZeptoMail profile supports its API and SMTP relay. SMTP and SMTPS use a username and password; the username defaults to emailapikey.

Before you begin#

Have an account with the provider that is enabled to send mail, a sender address accepted by that account, and credentials for the method you plan to use. Copy credentials from your own provider console. Do not include credential values in documentation, screenshots, or support requests.

Supported transport and settings#

Supported transport schemes#

The profile supports zeptomail+api (default), zeptomail+smtp, and zeptomail+smtps.

Required settings#

  • API: ZeptoMail API token (secret).
  • SMTP or SMTPS: username (defaults to emailapikey) and password (secret).
  • A webhook signing secret is optional in Jooosi Mail and enables HMAC signature verification when configured.

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select ZeptoMail 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#

Use Jooosi Mail’s Send a test email flow, select this connection, and send to an inbox you control. The test sends a real message. Confirm the attempt appears in Email Logs and review the provider response if it fails. See Send a test email.

Webhooks#

Supported events include soft and hard bounce, open, click, delivered, and feedback loop. Enable webhook ingestion and configure the provider callback to the URL displayed for this connection. If a webhook secret is saved, the adapter verifies the HMAC signature and timestamp; without a secret, it accepts unsigned callbacks.

Troubleshooting#

  • If authentication fails, check that the API token is in the API field or the SMTP password is in the password field.
  • If callbacks fail verification, check the shared secret and server clock; signatures outside the adapter’s five-minute timestamp window are rejected.