Source
Documentation (webhooks) — Lettermint
Checked for Lettermint on 1 Nov 2026
- Page
- https://lettermint.co/docs/platform/webhooks/introduction
- Checked
- 1 Nov 2026, 09:35 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:94fa1b133af0d3c2053a8ca6be764c343d66eab0840021041b106813517ed802
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Webhooks post Report an error
“Use webhooks to receive an HTTP POST request when a Lettermint event occurs. A webhook removes the need to poll the Team API for delivery updates.”
-
Webhook scopes Report an error
“You can use three webhook scopes: Team: The webhook receives events from all current and future projects and routes. Project: Select one or more projects. The webhook receives events from all current and future routes in those projects. Route: Select one or more routes. The routes can be in different projects.”
-
Webhook basic auth Report an error
“Use Basic Auth when your HTTPS endpoint requires a username and password. This works for team, project, and route webhooks, including test deliveries.”
-
Webhook credentials encrypted Report an error
“Lettermint encrypts saved credentials. The dashboard and API never return the saved username or password. The API returns has_basic_auth to show whether Basic Auth is configured.”
-
Webhook signature Report an error
“Every webhook delivery includes these headers: Header Description X-Lettermint-Signature HMAC-SHA256 signature for verification X-Lettermint-Event Event type (e.g., message.delivered) X-Lettermint-Delivery Delivery timestamp (Unix seconds) X-Lettermint-Attempt Retry attempt number (1, 2, 3...)”
-
Webhook https required Report an error
“Your endpoint must use HTTPS and a public address. Basic Auth does not permit deliveries to localhost or private network addresses. Lettermint does not follow redirects.”
-
Webhook request timeout Report an error
“The request timeout is 30 seconds.”
-
Webhook retry behavior Report an error
“We retry temporary failures with exponential backoff. Timeouts, HTTP 408, HTTP 429, and server errors can trigger retries. Other HTTP 4xx responses, including HTTP 401, do not trigger automatic retries.”
-
Webhook retry schedule Report an error
“Retry schedule (12 total attempts: 1 initial attempt + 11 automatic retries):”
-
Webhook retry window Report an error
“This schedule spans roughly 14 hours from the initial delivery attempt to the final automatic retry.”
-
Webhook manual retry Report an error
“You can retry a failed delivery from the webhook's deliveries in the dashboard, with the Webhook API, or through MCP. A retry sends the original payload right away and counts as an attempt.”
-
Webhook pausing Report an error
“If 20 deliveries in a row get no response from your endpoint, because the connection fails or the request times out, we pause requests to that webhook for one minute.”
-
Webhook auto disable Report an error
“We disable a webhook when every delivery to it has failed for 72 hours. A single successful delivery in that time keeps it enabled”
-
Webhook no redelivery when disabled Report an error
“Events that occur while a webhook is disabled are not delivered and are not sent later.”
-
Webhook delivery modes Report an error
“Delivery mode Whether the webhook receives Live events, Sandbox events, or both. New team, project, and route webhooks default to Live.”
-
Webhook machine events option Report an error
“Include machine events Whether message.opened and message.clicked webhooks include security scanner, preview, and generic bot observations. Supported privacy opens do not need this option. Disabled by default.”
-
Webhook signing secret rotatable Report an error
“Secret HMAC secret for signature verification (rotatable)”
-
Webhook multiple webhooks Report an error
“Create multiple webhooks when different systems need different event sets. Use one webhook with multiple targets when one system processes events from selected projects or routes.”
-
Webhook test delivery Report an error
“Use the Test Webhook button in the dashboard to verify your endpoint is working before sending real emails.”
-
Webhook API endpoints Report an error
“Use this request body with POST /v1/webhooks:”
-
Webhook idempotency Report an error
“Implement idempotency Use the event.id field to detect duplicate deliveries and prevent processing the same event twice:”
Scores citing this record
- The Agency Lead Sending API, SMTP & developer experience
- The Agency Lead Message logs, events & webhooks
- The Data Protection Officer Message logs, events & webhooks
- The Shop Operator Message logs, events & webhooks
- The Platform Engineer Sending API, SMTP & developer experience
- The Platform Engineer Message logs, events & webhooks
- The SaaS Developer Message logs, events & webhooks
- The Skeptic Message logs, events & webhooks