Skip to content
Jooosi
Account
JM Jooosi Mail

SendLayer

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 SendLayer profile provides API, SMTP, and SMTPS transports. The API key is only for the API scheme; the SMTP options require an SMTP username and password.

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 sendlayer+api (default), sendlayer+smtp, and sendlayer+smtps.

Required settings#

  • API: SendLayer API key (secret).
  • SMTP or SMTPS: SendLayer SMTP username and password; password is secret.
  • The profile does not expose host, port, or region settings.

Create the connection#

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

SendLayer events supported by the profile include delivered, open, click, bounce, unsubscribed, and spam complaint. Enable webhook ingestion and configure the provider callback to the URL shown for this connection. A saved connection webhook secret enables HMAC signature verification. Without a secret, unsigned callbacks are accepted; check webhook status for the active verification posture.

Troubleshooting#

  • If connection validation fails, make sure the API scheme has an API key or an SMTP scheme has both SMTP fields.
  • If test mail fails, check that the SMTP password belongs to the SMTP login and review the connection attempt details.