Skip to content
HookBridge Docs

Inbound Overview

Inbound means external providers send events to HookBridge first, then HookBridge forwards accepted events to your destination URL.

This separates two parts of the pipeline:

  • Ingest validation: token/signature/IP/timestamp checks at the edge
  • Forwarding delivery: retries, message status tracking, and replay controls to your destination

Flow

Section titled “Flow”
  1. Provider sends a webhook to your HookBridge ingest_url.
  2. HookBridge validates the request using your inbound endpoint settings.
  3. If validation passes, HookBridge creates an inbound message and forwards it.
  4. If forwarding fails, HookBridge retries and updates message status.
  5. If validation fails, the request is recorded as a rejection and is not forwarded.

API reference:

Next

Section titled “Next”
Personalize Examples

Enter your credentials to populate code examples throughout the docs.