Securessmtp Com Webhooks

generated: '2026-10-31'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://securessmtp.com/docs/guides/webhooks
sources:
- https://securessmtp.com/docs/guides/webhooks
- https://securessmtp.com/docs/events
description: SecureSMTP provides webhooks for a variety of email, form, and domain events.
events:
- event: email.sent
  description: We accepted the email and handed it to our mail server.
- event: email.delivered
  description: The receiving mail server accepted the email.
- event: email.bounced
  description: The receiving server refused the email for good.
- event: email.complained
  description: The recipient reported the email as spam.
- event: email.delayed
  description: The receiving server asked us to try again later; we keep trying.
- event: email.opened
  description: The email was opened (every open).
- event: email.clicked
  description: A tracked link was clicked (every click).
- event: email.unsubscribed
  description: A recipient unsubscribed from your site (first time only).
- event: email.suppressed
  description: 'Not sent: every recipient bounced, complained or unsubscribed before.'
- event: email.rejected
  description: 'Not sent: spam content or your plan’s limit.'
- event: email.held
  description: 'Not sent: a contact‑form notification held as spam.'
- event: email.failed
  description: 'Not sent: the send attempt failed.'
- event: form.submitted
  description: A form submission was stored.
- event: form.spam
  description: A form submission was classified as spam.
- event: domain.verified
  description: A sending domain passed its DNS check.
- event: domain.unverified
  description: A verified domain failed a later check.
- event: webhook.test
  description: You clicked Send test.
delivery:
  signature: X-QCS-Signature (sha256= HMAC‑SHA256 of raw JSON body, keyed with the webhook secret that starts with whsec_)
  content_type: application/json
note: No additional authentication headers are required; security relies on the HMAC signature verification using the secret shown when creating
  the webhook.
docs: https://securessmtp.com/docs/guides/webhooks