Source
Message logs, events & webhooks — found from sitemap — MailerSend
Checked for MailerSend on 1 Nov 2026
- Page
- https://www.mailersend.com/help/webhooks
- Checked
- 1 Nov 2026, 09:37 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:44a6d92c04f5f99cd60665c7eb89bb7b67f8e5e2db245f1878af2783d0ed4b19
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Webhooks realtime Report an error
“Webhooks allow you to subscribe to real-time notifications about various events that occur in MailerSend.”
-
Webhook events Report an error
“Popular events include Delivery, Soft bounce, Hard bounce, Open, Click, Unsubscribe, Spam complaint, Domain reputation changed and Account reputation changed.”
-
Webhooks v2 Report an error
“Webhooks 2.0 have launched! This makes webhook payloads lighter for better, faster performance.”
-
Webhooks v1 deprecation Report an error
“Webhooks 1.0 is deprecated and will be removed on December 1, 2026, so we recommend migrating to Webhooks 2.0 if you haven't already.”
-
Webhook pause toggle Report an error
“You can also pause the webhook by clicking on Edit and then on the Status toggle, moving it from Enabled to Disabled.”
-
Webhook test Report an error
“Under Events, click Test webhook.”
-
Webhook attempts retention Report an error
“You can consult all webhook attempts that have been made in the last 7 days in the Webhook attempts section of your webhook description page.”
-
Webhook timeout Report an error
“When your webhook receives a response other than a 2xx code from your endpoint URL, or if the endpoint doesn’t respond within 3 seconds, it will show up as a failed attempt”
-
Webhook retries Report an error
“If a webhook call fails, MailerSend will retry the call a couple of times, waiting 10 seconds between the first and second attempt and 100 seconds between the second and the third attempt”
2 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- 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 Message logs, events & webhooks
- The SaaS Developer Message logs, events & webhooks
- The Skeptic Message logs, events & webhooks