Due to their rather simple complexion, WebHooks are very popular among developers. They are already included in some of the popular services and Web APIs, offering multiple possibilities.
To make managing them easier, Microsoft is introducing ASP.NET WebHooks. This will largely simplify the process of sending and receiving WebHooks as a part of an ASP.NET application.
Microsoft describes the feature in the announcement:
- On the receiving side, it provides a common model for receiving and processing WebHooks from any number of WebHook providers. It comes out of the box with support for Azure Alerts, BitBucket, Dropbox, Dynamics CRM, GitHub, Kudu, Instagram, MailChimp, MyGet, PayPal, Pusher, Salesforce, Slack, Stripe, Trello, Visual Studio Team Services, WordPress, and Zendesk as well as IFTTT and Zapier, but it is easy to add support for more.
- On the sending side, it provides support for generating WebHooks as a result of changes in your service. It helps managing and storing subscriptions as well as sending event notifications to the right set of subscribers. This allows you to define your own set of events that users can subscribe to. ASP.NET WebHooks provides a lot of flexibility for sending and persisting WebHooks, scaling your solution up and out, as well as sending WebHooks from WebJobs and other places in addition to your Web Application.
The company states the two parts can be used both individually or jointly, depending on what type of service you need. This means you can use just the receiver part if you only need to receive WebHooks from other services or use just the sender part if you only want to send WebHooks to others.
Microsoft is also planning a port to the ASP.NET Core which should be out soon. In the meantime, those looking for more technical information can check out the official blog post. It features detailed overviews on receiving and sending WebHooks, complete with diagrams, as well as other information.