Protocols
Saved & recent

Webhooks

Also called: HTTP callback, event webhook

A webhook is an integration pattern in which a system sends an HTTP request to a registered endpoint when an event occurs. It lets the receiver learn about changes without repeatedly polling for them. The event format, authentication and delivery rules belong to the provider’s contract.

For a hypothetical repository, a push event can trigger an HTTP notification to a build service. That service verifies the delivery, records it and schedules work. Failures, retries and manual redelivery can require duplicate handling; ordering and automatic retries vary by provider. A successful HTTP acknowledgment can mean the event was accepted without proving the build already finished.

Read first
HTTP
Related
HTTP, Idempotency key, Authentication
Further reading
repository push receiver webhook HTTP request verify deduplicate possible provider redelivery durable accepted-event queue 2xx acceptance acknowledgment later build
A hypothetical receiver verifies and records a webhook before acknowledging acceptance. The build runs later. Possible redelivery rejoins duplicate handling; retry and ordering behavior depend on the provider’s contract.

View in the full Protocols collection