This and the fact that API has request-response cycle, whereas webhook just sends data oneway. That's how I understood it.

Yes

In some cases your code is posible but many times it is not possible to poll the server for changes and then send a request A better explanation brought to you by the new age internet : Webhooks work in a different way. With webhooks, you don't initiate a request to the server; instead, the server initiates a request to your client when an event occurs. The server "calls back" to a URL provided by your client (the webhook endpoint), and sends data about the event that triggered the webhook. So, in the case of using webhooks, you don't need to constantly poll the server for updates or events. Instead, the server sends you the data automatically, as soon as the event occurs. This can be more efficient and reduce latency, since you don't need to repeatedly send requests to check for updates. In summary, while both APIs and webhooks can be used to send and receive data, the main difference is in how the data is pushed or pulled. APIs use a request-response model where the client initiates the request, while webhooks use a push model where the server initiates the request to the client.

I haven't used webhooks yet, but my understanding is: Webhooks are basically callback URLs that the client provides to the server. These URLs needs to be called by the server when a specific event occurs. So when the event occurs, server will just send a post request to that URL (by probably creating a proxy client), and some server SHOULD be listening at that URL for requests, otherwise there is no point.

@@XEQUTE This explains it better than the video

pleasure buddy@@wessamabozeid8522

You can request as soon as an event takes place

Facts! 💯

Stfu

Stfu

*STFU*

stfu

STFU