Skip to content
Jooosi
Account
JM Jooosi Mail

AhaSend

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

AhaSend sends mail through either its API transport or SMTP. The API transport is the default and needs an API key. Choose SMTP when you intend to use AhaSend SMTP credentials. Jooosi Mail also supports AhaSend delivery webhooks for connection-level event tracking.

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: ahasend+api (default), ahasend+smtp.
  • Required settings: ahasend+api: AhaSend API key (secret). ahasend+smtp: AhaSend SMTP username and AhaSend SMTP password (secret).
  • Optional settings: There are no additional provider configuration fields for this profile. If you enable webhooks, a Webhook secret is required.

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#

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

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. For supported webhooks, see the provider note and Provider webhooks guide.

Webhooks#

AhaSend webhooks are supported. Enable Webhooks under Advanced settings, enter the same shared secret that you configure for the callback in AhaSend, save, then use the endpoint displayed on the connection. The adapter verifies AhaSend signatures using that secret, so the secret is mandatory when webhooks are enabled. For endpoint and event setup, follow the shared Provider webhooks guide.

Troubleshooting#

  • Confirm that the credential type matches the selected transport: the API key is not the SMTP password.
  • If webhooks are rejected, make sure the connection secret matches the shared signing secret configured for AhaSend.

Provider reference: https://ahasend.com/docs.