This is how Wikipedia defines webhooks: A webhook in web development is a method of augmenting or altering the behavior of a web page or web application with custom callbacks. These callbacks may be maintained, modified, and managed by third-party users and developers who may not necessarily be affiliated with the originating website or application.
There are two ways your apps can communicate for information: polling and webhooks. Polling is when you go asking the app for some information every time. Webhooks are when the app automatically sends the information over to a specific URL every time it's available.
Webhooks are basically automated messages containing an information payload sent from Brizy Cloud when something happens. They are sent to a unique URL that you can set up.
Webhooks are similar to APIs—but simpler. An API is a full language for an app with functions or calls to add, edit, and retrieve data. The difference is, with an API, you have to do the work yourself. If you build an application that connects to another with an API, your application will need to have ways to ask the other app for new data when it needs it.
Webhooks, on the other hand, are for one specific part of an app, and they're automated. In other words, a webhook is a simple, one-to-one connection that runs automatically.
In Brizy Cloud we offer webhooks for all your Assets including custom Assets:
And Actions on Create, Update and Delete.
This means that when the [Asset] (Page, Blog, etc) is [Action] (Created, Updated, Deleted), we automatically send a payload with all the information for that specific Asset to your selected custom URL.
The information sent is signed and you can find the key on the Webhooks listing page.
You use this signature ID to verify and validate that the data comes from us.