That’s a good question to start with, although an even better question might be this: are there any Identity Cloud events that you need to know about the minute they happen? If there are, then yes, maybe you do need Webhooks v3. If there aren’t, then maybe you don’t.
So are there any Identity Cloud events that you need to know about the minute they happen? The best way to answer that question is to consider some common scenarios and see if they apply to you. For example, suppose that users who register on your site are automatically signed up for your monthly newsletter or your weekly coupon specials; users who aren’t registered don’t qualify for these special offers. In a case like that, a webhook subscription that monitors for the creation of new user accounts and the deletion of existing user accounts might come in handy. Why? Well, that way, when a user creates a new account, a webhook notification can be sent and the user can instantly be added to the newsletter subscriber list or the weekly coupon list. Likewise, when a user deletes their account, another webhook notification can be sent and the user removed from those lists.
Note. This is a good time to point out that the role of Webhooks v3 is simply to send notifications that an account has been created, deleted, or updated. After the notification has been received, Webhooks v3 is no longer part of the process: at that point, you’re on your own. In other words, we’ll let you know that Karim Nafir has just registered. If that means that Karim should now be added to the newsletter subscriber list, well, that’s a task you’ll need to perform on your own.
Or consider another example. Suppose you have a website designed for healthcare professionals: membership in the site is contingent on the user being a registered healthcare professional. The Identity Cloud cannot verify whether or not a prospective user is a healthcare professional. However, the Identity Cloud can notify you the moment a new user registers for an account, and thus set in motion a process for verifying that the user meets the necessary requirements for membership on your site. Those are the kind of situations that webhooks were made for.
That said, you should also keep in mind that Akamai offers other ways to review eventing information, even if that information is not delivered in real time. For example, if you’re primarily interested in who your users are – what countries they come from, what time of the day they’re most likely to access your site, how many of them are under the age of 30 – then you might want to check out Customer Insights. If what you’re really interested in is what your Console agents are doing – creating other agents, promoting flows, resetting API client secrets – then take a look at Console Audit Logs.