Pull endpoints

Turn incoming webhooks into an API your workers can poll.

Hookbridge accepts and stores incoming events. Your worker lists them, fetches the payloads it can process, and acknowledges completed work on its own schedule.

SourceExternal providers
Store until requested
Delivery layerHookbridge storage
DestinationYour workers
How it works

Consume webhooks without accepting inbound traffic.

Pull endpoints fit batch jobs, restricted networks, and consumers that need explicit control over backpressure.

01

Create a pull endpoint

Configure verification and receive a unique ingestion URL for the provider.

02

List stored events

Filter by status, event type, or time and paginate through available records.

03

Acknowledge completed work

Mark one event or a batch as delivered after your worker finishes processing.

Product view

Pull endpoints in the current console

The preview follows the existing Pull tab and its endpoint table. The endpoint values are examples.

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

Endpoints

Manage webhook delivery destinations

OutboundInboundPull

Pull Endpoints (2)

NameIngestion URLStatusCreatedActions
Batch ordersreceive.hookbridge.ioUnique private ingestion URLActiveJul 12, 2026
Finance workerreceive.hookbridge.ioUnique private ingestion URLActiveJul 8, 2026
SDKs

List and acknowledge events from any supported SDK.

Each SDK exposes the pull event lifecycle directly, including cursor pagination and batch acknowledgment.

Open the API reference
List stored events
curl "https://api.hookbridge.io/v1/pull-endpoints/$ENDPOINT_ID/events?status=stored" \
  -H "Authorization: Bearer $HOOKBRIDGE_KEY"

# => {"data":[...],"meta":{"has_more":false,"next_cursor":""}}
Included

Controls for the whole event lifecycle

01

Stored events

Incoming requests wait in Hookbridge until a consumer retrieves them.

02

Cursor pagination

Move through large event sets without page numbers shifting under concurrent writes.

03

Filtering

Request stored or delivered events by event type and time range.

04

Batch acknowledgment

Acknowledge up to 1,000 processed events in one idempotent request.

05

Reprocessing

Delivered events remain readable until retention expires or they are deleted.

06

Outbound-only networking

Workers consume events through outbound API calls without exposing a public server.

Start on the free plan

Let your worker decide when the next event moves.

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