What is a Webhook?

Learn what webhooks are and why you need them. In this guide, you’ll discover how they may be used with your apps and you will start using them.

Sometimes it can be useful to have a trace of the activities that have taken place on your

The fallback content to display on prerendering

. This is even more true when it comes to sensitive subjects such as authentication or the creation and manipulation of identity data. That's why Cryptr offers you tools that will allow you to keep an eye on all these activities. Whether on SCIM exchanges or on the activity of your SSO, you will be able to view all events in real time. This is made possible through the use of Webhooks.

📄️ How to setup a webhook

Follow these steps on how to set up a webhook and get started to create a webhook that sends real-time data.

🗃️ Events

2 items

📄️ How to test a webhook

Learn how to test your webhooks to improve their processing performance before they go into production.

📄️ How to secure a webhook

Check the events that Cryptr sends to your webhook endpoints for more security and make sure that these events have not been sent by a third party.

📄️ How to manage hook delivery attempts and retries

Sometimes your application can't handle receiving webhook events. We give you the best practices to manage your exceptions.

Keep an eye on your app in real-time thanks to the webhooks

Thanks to Webhooks, you can receive real-time notifications directly on your

The fallback content to display on prerendering

. These keep you informed of important events. These notifications will be sent from Cryptr services directly to your

The fallback content to display on prerendering

using the HTTPS protocol in the form of JSON objects. You can then process these notifications whether to keep track of these events or to perform more complex actions on your systems. If you want to learn more about supported events, please see the webhooks documentation.

What are webhooks for?

Webhooks are, to put it simply, functions that are usually triggered by events. When an event is recorded, the source site or

The fallback content to display on prerendering

(here Cryptr) will send an HTTP(S) request to the destination site (you). This is defined in the webhook by a URL. The request contains a different payload depending on the type of event and the result obtained. For example, creating a user is an event but it can be either a success or a failure. There are many types of events that are the basis of Webhooks, these can be found in the events list.