Outbound delivery

Send customer webhooks without owning the delivery loop.

Publish an event through one API. Hookbridge stores the payload, signs the request, delivers it to the customer endpoint, and schedules retries when the destination is unavailable.

SourceYour application
Store, sign, deliver, retry
Delivery layerHookbridge
DestinationCustomer endpoints
How it works

Your request ends before the delivery work begins.

Hookbridge returns a message ID after the payload is stored and queued. Customer latency and retries stay outside your application request path.

01

Create a destination

Add the customer's HTTPS endpoint and choose its rate and burst limits.

02

Publish the event

Send the endpoint ID and JSON payload through an SDK or the HTTP API.

03

Inspect and recover

Review every attempt, retry pending messages, or replay retained deliveries.

Product view

Outbound endpoints in the current console

The preview below follows the existing Endpoints page structure and fields. The endpoint values are examples.

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

Endpoints

Manage webhook delivery destinations

OutboundInboundPull

Send Endpoints (2)

Endpoint IDURLStatusDescriptionCreatedActions
ep_customer_billingapi.customer.comhttps://api.customer.com/webhooksActiveCustomer billingJul 12, 2026
ep_crm_eventsevents.customer.comhttps://events.customer.com/hookbridgeActiveCRM eventsJul 8, 2026
SDKs

Send from the language already in your stack.

The SDKs wrap the same send API and return the Hookbridge message record.

Open the API reference
Send an event
curl -X POST https://send.hookbridge.io/v1/webhooks/send \
  -H "Authorization: Bearer $HOOKBRIDGE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endpoint_id":"ep_customer_billing","payload":{"event":"invoice.paid"}}'

# => {"data":{"message_id":"01935abc-...","status":"queued"}}
Included

Controls for the whole event lifecycle

01

Automatic retries

Retryable failures are handled automatically with exponential backoff and jitter.

02

HMAC signing

Every outbound request can be verified using its timestamp and HMAC-SHA256 signature.

03

Idempotent requests

Attach an idempotency key when your application may repeat the same send request.

04

Endpoint rate limits

Control sustained delivery and short bursts independently for each destination.

05

Attempt timing

Inspect DNS, TCP, TLS, time to first byte, and total response time.

06

Replay

Redeliver retained messages from the console or API after a customer fixes an endpoint.

Start on the free plan

Send the first customer event through Hookbridge.

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