Webhook
A webhook sends an HTTP notification to another system when a specified event occurs.
A webhook is an HTTP notification a system sends to a registered address when a specified event occurs. The receiver does not need to keep asking for changes. Payload, authenticity checks and possible retries depend on the provider.
A fictional shop notifies an integration of order W-240 through event evt-17. The integration accepts the message and handles the ERP transfer separately. A received status therefore does not prove a completed ERP order.
Webhooks may arrive repeatedly or out of order unless the provider guarantees otherwise. Receivers need appropriate matching and retry rules. Polling, by comparison, means repeatedly querying the other system actively.
Sources
Related terms
- IdempotencyAn idempotent operation has the same intended effect on system state when repeated identically as when performed once.
- Retry strategyA retry strategy defines which failures to retry, the waiting intervals and the limit on further attempts.
- Server-sent eventsServer-sent events carry text notifications from server to client over HTTP, for example about the progress of a background job.
- Entity tagAn ETag identifies a particular representation version of an HTTP resource and supports conditional reads or changes.
- Cross-Origin Resource SharingCORS controls browser access to responses across origin boundaries. It replaces neither API login nor permission checks.
- Electronic Data InterchangeEDI transfers structured business documents between systems. Format, partner profile, data mapping and responses need to agree.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.