PufferPost uses one API transport in Jooosi Mail. A single API key is required; the profile does not expose SMTP or additional endpoint settings.
Before you begin#
- You need access to the provider account and the Jooosi Mail Connections screen. If the provider requires sender or domain verification, complete it in the provider account first.
- Copy credentials directly from the provider’s own console into the matching Jooosi Mail field. Keep secret values private; never include them in screenshots or support messages.
Consult provider sending documentation for any provider-side setup requirements.
Supported transport and settings#
pufferpost+api(default and only supported scheme): Required: PufferPost API key (secret).
Create the connection#
- In WordPress admin, open Jooosi Mail → Connections and choose New connection.
- Enter a descriptive Connection name and select PufferPost 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.
Have the API key ready from your PufferPost account before adding the connection. Copy it from the provider’s own console into Jooosi Mail; do not include the value in documentation, screenshots, or support messages.
For the shared form workflow, see Connect a provider.
Verify delivery#
Use Send a test email with a recipient you control; it sends a real message through this connection. Check its status and the email log for the provider response.
Webhooks#
This profile does not declare a provider webhook adapter. Track delivery outcomes in the Jooosi Mail email logs. See the shared email logs guide.
Troubleshooting#
- For missing-field validation, confirm the scheme and fill all required settings listed above.
- After a failed test, re-copy the matching credential and inspect the connection status and email log.
- If Jooosi Mail reports incomplete configuration, check that the API key is saved in the API Key field and that the
scheme remains
pufferpost+api. The profile offers no SMTP alternative or region field to adjust.