Inbound webhooks

Put a stable URL between providers and your application.

Accept webhooks from Stripe, GitHub, Shopify, or another provider. Hookbridge can verify the request, store it, and forward it to your service with retries.

SourceExternal providers
Verify, store, forward, retry
Delivery layerHookbridge
DestinationYour application
How it works

Change your backend without changing the provider URL.

The ingestion URL remains stable while the delivery URL can move between environments or services.

01

Create an inbound endpoint

Choose the delivery URL and configure HMAC, token, or IP verification when needed.

02

Give the URL to the provider

The unique ingestion URL accepts and stores each valid request.

03

Forward to your service

Hookbridge sends the original payload and retries when your application is unavailable.

Product view

Inbound endpoints in the current console

The preview uses the existing Inbound tab, table columns, and create action. The endpoint values are examples.

Current console structure with example endpoint data
HBConsole
DashboardAnalyticsMessagesExportsAlertsAPI KeysEndpointsProjectsBilling
Jjay@example.com

Endpoints

Manage webhook delivery destinations

OutboundInboundPull

Receive Endpoints (2)

NameDelivery URLStatusCreatedActions
Stripe billingapi.example.comhttps://api.example.com/webhooks/stripeActiveJul 12, 2026
GitHub appapi.example.comhttps://api.example.com/webhooks/githubActiveJul 8, 2026
SDKs

Create inbound endpoints from every supported SDK.

Configure endpoints in code when they belong in your provisioning workflow.

Open the API reference
Create an inbound endpoint
curl -X POST https://api.hookbridge.io/v1/inbound-endpoints \
  -H "Authorization: Bearer $HOOKBRIDGE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Stripe billing","url":"https://api.example.com/webhooks/stripe"}'

# => ingest_url is returned once. Store it when you create the endpoint.
Included

Controls for the whole event lifecycle

01

Stable ingestion URL

Providers keep sending to the same URL while your internal delivery destination changes.

02

Request verification

Check HMAC signatures, static tokens, or source IPs before accepting a request.

03

Durable storage

The payload is stored before forwarding begins and remains available through retention.

04

Forward retries

Timeouts and retryable responses follow the same recorded delivery schedule.

05

Rejected requests

Review requests blocked by invalid secrets, allowlists, methods, or payload limits.

06

Replay

Forward the original retained payload again after your application recovers.

Start on the free plan

Give the next provider a Hookbridge URL.

Use the API, an SDK, or the console. No credit card is required.