Skip to content
HookBridge Docs

Inbound Webhooks Guide

Use this guide when external providers send events into HookBridge and HookBridge forwards them to your destination.

Inbound Flow

Section titled “Inbound Flow”
  1. External provider POSTs to your HookBridge ingest_url.
  2. HookBridge validates request rules (token, HMAC, IP allowlist, etc.).
  3. Accepted events are forwarded to your configured destination URL.
  4. Failed forwards retry; rejected ingests are recorded as rejections.

Idempotency (Inbound)

Section titled “Idempotency (Inbound)”

Inbound dedupe is configured per endpoint via idempotency_header_names.

Terminal window
curl -X PATCH https://api.hookbridge.io/v1/inbound-endpoints/YOUR_INBOUND_ENDPOINT_ID \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "idempotency_header_names": ["Idempotency-Key", "X-Event-ID"]
  }'

Behavior notes:

  • Dedupe keys are derived from configured header values.
  • Stable provider event IDs improve dedupe quality.
  • Header order matters because the list is ordered.

Retry Behavior (Inbound)

Section titled “Retry Behavior (Inbound)”

Forwarding status progression:

  • queued
  • delivering
  • succeeded
  • pending_retry
  • failed_permanent

Recovery and control actions:

  • Replay one message: POST /v1/inbound-messages/{id}/replay
  • Replay many messages: POST /v1/inbound-messages/replay-all
  • Pause endpoint: POST /v1/inbound-endpoints/{id}/pause
  • Resume endpoint: POST /v1/inbound-endpoints/{id}/resume

Monitoring (Inbound)

Section titled “Monitoring (Inbound)”
  • Logs: GET /v1/inbound-logs
  • Metrics: GET /v1/inbound-metrics
  • Time series: GET /v1/inbound-metrics/timeseries
  • Rejections: GET /v1/inbound-rejections
Section titled “Related”
Personalize Examples

Enter your credentials to populate code examples throughout the docs.