Skip to content

Inbound Monitoring and Recovery

Inbound operations have two different failure surfaces, and you need visibility into both:

  • Ingest validation failures (rejections): request was blocked and never forwarded.
  • Forwarding delivery failures (pending_retry / failed_permanent): request was accepted, but downstream delivery had issues.

Monitoring both surfaces makes incident response faster because you can quickly tell whether the problem is provider/auth configuration or destination availability.

  1. Open Messages and switch to inbound direction.
  2. Review message statuses to track retry backlog and permanent failures.
  3. Review Rejections for ingest-side validation failures.
  4. Use endpoint filters to isolate one integration at a time.
  5. Apply recovery actions (replay, replay-all, pause, resume) as needed.

API reference:

Terminal window
curl "https://api.hookbridge.io/v1/inbound-logs?limit=50" \
-H "Authorization: Bearer YOUR_API_KEY"
curl "https://api.hookbridge.io/v1/inbound-metrics?window=24h" \
-H "Authorization: Bearer YOUR_API_KEY"
curl "https://api.hookbridge.io/v1/inbound-metrics/timeseries?window=24h&inbound_endpoint_id=YOUR_INBOUND_ENDPOINT_ID" \
-H "Authorization: Bearer YOUR_API_KEY"
Terminal window
curl "https://api.hookbridge.io/v1/inbound-rejections?limit=50&inbound_endpoint_id=YOUR_INBOUND_ENDPOINT_ID" \
-H "Authorization: Bearer YOUR_API_KEY"
Terminal window
curl -X POST https://api.hookbridge.io/v1/inbound-messages/YOUR_INBOUND_MESSAGE_ID/replay \
-H "Authorization: Bearer YOUR_API_KEY"
  1. Check rejections first if expected inbound volume drops.
  2. Check retry/failure statuses if inbound volume is normal but downstream side effects are missing.
  3. Confirm the fix with one replayed message.
  4. Use replay-all for broader recovery only after validation.
Personalize Examples

Enter your credentials to populate code examples throughout the docs.