The case for webhooks
Webhooks are a better way for web applications to communicate with each other in realtime. If you provide your users with an API, and they want to listen for new data, they'll do so by "polling"—where they periodically make requests to the API. With webhooks, a user provides a URL, and your application sends new data to their application with a POST request.
Empower your users
- Webhooks let your users integrate with your application in realtime; it's a much better experience than polling your API for new data.
- If you have an API, your users may expect you to support webhooks. Worst case scenario, they'll be pleasantly surprised.
- By encouraging your users to integrate your application with their internal workflows and systems, the likelihood that they'll switch to a competitor is reduced.
Empower your (future) partners
You may already integrate with popular services such as GitHub and Slack, but do you integrate with the thousands of other services that your customers may use?
It makes sense to integrate with the services that a majority of your customers use, but there's always a limit; webhooks can help the remaining services (and your customers) integrate with *you*.Adding webhooks to your app »