Skip to content
Jooosi
Account
JM Jooosi Mail

Provider webhooks

Enable provider callbacks, check verification support, and inspect webhook events.

Browse documentation
Overview
Contents
On this page
  1. Enable a webhook
  2. Check support and verification
  3. Inspect webhook status and events

Provider webhooks let supported services report delivery events to Jooosi Mail. The plugin stores received events and projects them into WordPress hooks so delivery and routing health can be updated.

Enable a webhook#

  1. Open Jooosi Mail → Connections and edit the provider connection.
  2. In its webhook settings, enable ingestion and configure the verification secret or other verification details required by that provider.
  3. Copy the webhook URL shown for the connection and add it in the provider’s dashboard.
  4. Send or replay a provider event, then check webhook status and recent events.

The endpoint follows this pattern: /wp-json/jooosi-mail/v1/webhook/{connection_id}. Replace {connection_id} with the ID of the connection receiving callbacks.

Check support and verification#

Webhook support depends on the connection profile and adapter. Current adapters include AhaSend, Bird, Brevo, MailerSend, Mailgun, Mailjet, Mailomat, Mailtrap, Mandrill, Postmark, Resend, SendGrid, SendLayer, SMTP2GO, SparkPost, Sweego, toSend, and ZeptoMail, plus a generic fallback parser.

Verification may use a shared secret or HMAC, a provider public key, an IP allowlist, or an unsigned callback where a provider offers no stronger method. Some adapters require secret material and will report an unsupported verification state until it is configured. A connection with webhook ingestion disabled returns 404 to callbacks.

Inspect webhook status and events#

Run these WP-CLI commands from the WordPress installation:

  • wp jooosi-mail webhook:status checks configured connections.
  • wp jooosi-mail webhook:status --all=true includes every connection.
  • wp jooosi-mail webhook:events --limit=20 lists recent events.
  • wp jooosi-mail webhook:events --connection-id=3 filters events to one connection.

Replace 3 with your connection ID. See Provider profiles and transports for profile capabilities.