Webhook
Problem statement:
A consuming application desires to be informed of any change of state on a specific record or records; for example, updating or adding customers in a CRM SaaS, currency exchange rates from a foreign exchange (forex) application, or even new posts on a user's blog.
The majority of APIs only support these types of requirements by having the consuming application constantly poll for changes. This means that the consuming application has to make frequent API calls to find out any changes of state in a desired resource. Not only is this highly inefficient, as calls may result in empty payloads when there haven't been any updates, but it could also affect the user experience, especially when the behavior is reflected ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access