Webhook
A webhook (or WebHook), in web development, is a method of augmenting or altering the behavior of a web page, or web application, with custom callbacks. These callbacks may be maintained, modified, and managed by third-party users and developers who may not necessarily be affiliated with the originating website or application. The term "webhook" was coined by Jeff Lindsay in 2007 from the computer programming term Hook.[1]
Overview
Webhooks are "user-defined HTTP callbacks".[2] They are usually triggered by some event, such as pushing code to a repository[3] or a comment being posted to a blog.[4] When that event occurs, the source site makes an HTTP request to the URI configured for the webhook. Users can configure them to cause events on one site to invoke behaviour on another. The action taken may be anything. Common uses are to trigger builds with continuous integration systems[5] or to notify bug tracking systems.[6] As they use HTTP, they can be integrated into web services without adding new infrastructure.[7] However there are also ways to build a message queuing service on top of HTTP—some RESTful examples include IronMQ and RestMS.
In November 2012, the originator of the concept wrote about the next evolution in his thinking, the Evented Web.
See also
References
| ||||||||||||||||||||||||||||||||||||||||||||