Webhooks events

Webhooks are automatic messages sent from an application when an event occurs. We will explain how to understand these events and manage them.

This part will provide you with all the information you need to understand the events.

Webhooks allow you to be informed of certain events in real time on one or more of your

The fallback content to display on prerendering

. It is therefore important to understand what these correspond to and how they are used.

An event is an action that takes place at a given time within your

The fallback content to display on prerendering

. These are important and therefore it is worth keeping track of them or just being notified when one of them occurs. The creation of a user, its update, its deletion, its deactivation or even a

The fallback content to display on prerendering

are examples of events that it is interesting to take into account. This is why when one of them occurs we create an Event object. If you have created a webhook associated with this type of event, we send it to your

The fallback content to display on prerendering

via a POST request.

Despite their importance, some of these events may not necessarily interest you. Having information can, indeed, be interesting, but having too much of it can quickly make the work laborious and overload your

The fallback content to display on prerendering

. It is for this reason that Webhooks have been designed to be able to select only certain types of events.

1 Two families of Events

At Cryptr there are different families of Events. For example, some events are more focused on SSO while others are more focused on Directory Sync. However, all Webhooks are used in the same way. This way your experience will be simplified. We will see in the following how to identify the different events and how to use only the ones we need.

These families have their own events which are defined in the Webhooks by an Event Code.

2 Events list

For the full events list you can check the event list page.