The toSend profile sends through the toSend API. This profile exposes no SMTP transport and supports signed webhook event ingestion.
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 tosend+api only (default).
Required settings#
- API key is required and secret.
- For webhook ingestion, the connection also requires a webhook secret.
Create the connection#
- In WordPress admin, open Jooosi Mail → Connections and choose New connection.
- Enter a descriptive Connection name and select toSend in Profile.
- Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
- Review the sender, routing, and advanced settings for this connection.
- 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#
The adapter normalizes bounce and complaint callbacks. Enable webhook ingestion and configure toSend to post to the callback URL shown for this connection. The HMAC signing secret is required; without it, verification is unsupported and callbacks are rejected.
Troubleshooting#
- If the connection will not save, check that the API key is present.
- If delivery works but events do not appear, confirm the webhook secret, callback URL, and enabled status, then inspect Webhook Logs.