Mailgun webhook events
9 Mailgun event types in 2 resources. 9 have sample payloads.
These pages cover event webhooks, which report on email you send. Inbound Routes, which post email you receive through forward() and store() actions, have no event types and are covered in the Production guide.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
delivery
accepted
documented official schema
accepted Mailgun accepts a send request and queues the message
Identified by event-data.event field in the body
Resource delivery
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
delivered
documented official schema
delivered Recipient's mail server accepts the message
Identified by event-data.event field in the body
Resource delivery
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
failed
documented official schema
failed Delivery fails, with severity set to permanent or temporary
Identified by event-data.event field in the body
Resource delivery
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
permanent_fail
documented official schema
permanent_fail Permanent delivery failure, sent as failed with severity permanent
Identified by event-data.event field in the body
Resource delivery
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
temporary_fail
documented official schema
temporary_fail Temporary delivery failure, sent as failed with severity temporary
Identified by event-data.event field in the body
Resource delivery
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
engagement
opened
documented official schema
opened Recipient opens the message, with open tracking on
Identified by event-data.event field in the body
Resource engagement
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
clicked
documented official schema
clicked Recipient clicks a tracked link
Identified by event-data.event field in the body
Resource engagement
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
unsubscribed
documented official schema
unsubscribed Recipient clicks the unsubscribe link, with unsubscribe tracking on
Identified by event-data.event field in the body
Resource engagement
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
complained
documented official schema
complained Recipient reports the message as spam through a feedback loop
Identified by event-data.event field in the body
Resource engagement
{
"signature": { … },
"event-data": { … }
} From Mailgun docs
-
Content type
application/json
Route Mailgun events by type.
Event Gateway receives every Mailgun delivery and filters and routes it by event type, so each service gets only the events it handles.