> I just generally feel that perhaps this article and what you are referring to have something very specific in mind when you talk about webhooks and what they'

> I just generally feel that perhaps this article and what you are referring to have something very specific in mind when you talk about webhooks and what they're used for. I'm not the author or GP but I think you're right and can give my two cents. The specific thing these authors have in mind is a SaaS that offers an HTTP API to manipulate data and a set of HTTP webhooks to notify users about changes in the data. *If* the only thing SaaS users do within their webhook handler is make an API request back to the same SaaS, then the argument is there's a bunch of unnecessary work to shuffle bits back and forth across the internet when the SaaS could just offer to run a function. > I'd just argue that there is a much broader set of use cases out there for webhooks... Agreed, which is why there are many commenters here who are confused. The "webhooks suck" take is overcooked without context.