Skip to content
Jooosi
Account
JM Jooosi Mail

Sweego

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 Sweego profile provides API and SMTP transports. SMTP requires explicit endpoint settings; API uses an API key.

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 sweego+api (default) and sweego+smtp. There is no SMTPS scheme.

Required settings#

  • API: Sweego API key (secret).
  • SMTP: host, positive port, Sweego SMTP login (username), and password (secret).
  • If webhook ingestion is enabled, a webhook secret is required. The adapter expects a Base64-encoded shared secret for signature verification.

Create the connection#

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

Sweego event types include sent, delivered, soft and hard bounce, unsubscribe, complaint, click, and open. Enable webhook ingestion and configure the provider callback to the URL shown for this connection. The adapter requires the shared secret and rejects callbacks if it is missing or invalid.

Troubleshooting#

  • If SMTP validation fails, check that host, port, username, and password are all present.
  • If webhook status is unsupported or callbacks fail, verify the saved signing secret is Base64 encoded and that ingestion is enabled.