Inbound Message Operations

Why You Would Use This

Inbound message operations are your day-to-day tools for investigating delivery history and recovering failed forwards after ingest has already succeeded.

Use single-message replay for targeted fixes. Use replay-all when you need to recover a known set of messages after an incident.

Console Workflow

1. Open Messages and switch direction to Inbound.
2. Filter by endpoint or status.
3. Open a message to inspect details.
4. Use Replay for a single-message recovery.
5. Use Replay All when broader recovery is needed.

API Workflow

API reference:

• Inbound messages tag
• Replay inbound message
• Replay all inbound messages
• Replay batch inbound messages

# Get one inbound message
curl https://api.hookbridge.io/v1/inbound-messages/YOUR_INBOUND_MESSAGE_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

# Replay one message
curl -X POST https://api.hookbridge.io/v1/inbound-messages/YOUR_INBOUND_MESSAGE_ID/replay \
  -H "Authorization: Bearer YOUR_API_KEY"

# Replay many messages by filter
curl -X POST "https://api.hookbridge.io/v1/inbound-messages/replay-all?status=failed_permanent&inbound_endpoint_id=YOUR_INBOUND_ENDPOINT_ID&limit=100" \
  -H "Authorization: Bearer YOUR_API_KEY"

Replay a batch of specific messages by ID

curl -X POST https://api.hookbridge.io/v1/inbound-messages/replay-batch \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message_ids": ["INBOUND_MESSAGE_ID_1", "INBOUND_MESSAGE_ID_2"]}'

The response includes per-message results indicating which messages were replayed, which failed, and why.

Notes

• replay-all requires a status filter and supports optional inbound_endpoint_id and limit.
• replay-batch accepts up to 100 message IDs per request.
• Single-message replay can return a replay-limit error if the message has already been replayed too many times.