Replay

Replay lets you re-deliver any previously received message to its webhook endpoint.

When to Use Replay

• Failed deliveries — retry a message that ended up in the DLQ after fixing the underlying issue
• Testing — re-send a message to verify your webhook handler works correctly
• Recovery — re-process messages after deploying a fix to your application

Replay a Message

curl -X POST http://localhost:8080/replay/{message_id} \
  -H "X-API-Key: your-api-key"

Response:

{
  "status": "queued"
}

The message is re-queued for delivery. It goes through the normal delivery pipeline: the stored raw email is re-parsed, matched to its route, and delivered to the webhook URL.

CLI

mxhook replay msg-123

See the CLI reference for details.

Notes

• Replay uses the current route configuration. If you've changed the route's webhook URL since the original delivery, the replayed message goes to the new URL.
• The replayed message gets a fresh set of retry attempts.
• The original message's raw .eml file must still be in storage for replay to work.