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

Mailgun accepts a send request and queues the message

Identified by event-data.event field in the body Resource delivery

mailgun-accepted.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

delivered

documented official schema

Recipient's mail server accepts the message

Identified by event-data.event field in the body Resource delivery

mailgun-delivered.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

failed

documented official schema

Delivery fails, with severity set to permanent or temporary

Identified by event-data.event field in the body Resource delivery

mailgun-failed.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

permanent_fail

documented official schema

Permanent delivery failure, sent as failed with severity permanent

Identified by event-data.event field in the body Resource delivery

mailgun-permanent-fail.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

temporary_fail

documented official schema

Temporary delivery failure, sent as failed with severity temporary

Identified by event-data.event field in the body Resource delivery

mailgun-temporary-fail.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

engagement

opened

documented official schema

Recipient opens the message, with open tracking on

Identified by event-data.event field in the body Resource engagement

mailgun-opened.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

clicked

documented official schema

Recipient clicks a tracked link

Identified by event-data.event field in the body Resource engagement

mailgun-clicked.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

unsubscribed

documented official schema

Recipient clicks the unsubscribe link, with unsubscribe tracking on

Identified by event-data.event field in the body Resource engagement

mailgun-unsubscribed.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as JSON

complained

documented official schema

Recipient reports the message as spam through a feedback loop

Identified by event-data.event field in the body Resource engagement

mailgun-complained.json
{
  "signature": { … },
  "event-data": { … }
}

From Mailgun docs

  • Content type application/json

Send example to Inspect → View as 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.

Not affiliated with Mailgun. Facts are compiled from public sources and linked inline.