Emailit supports API and SMTP-based delivery. The API scheme uses an API key. Both SMTP schemes use Emailit’s SMTP API key, entered in the SMTP credential field. Select the scheme that matches how you intend to connect.
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: emailit+api (default), emailit+smtp, emailit+smtps.
- Required settings: emailit+api: Emailit API key (secret). emailit+smtp or emailit+smtps: Emailit SMTP API key (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#
- In WordPress admin, open Jooosi Mail → Connections and choose New connection.
- Enter a descriptive Connection name and select Emailit 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#
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.
Webhooks#
This profile does not declare provider webhooks. Use Jooosi Mail email logs to inspect delivery outcomes.
Troubleshooting#
- The SMTP field expects an Emailit SMTP API key, not a separate username and password.
- If authentication fails, recheck the scheme and credential type, then use the error shown in the Jooosi Mail email log to guide the next check.
Provider reference: https://docs.emailit.com.