Please enter the following details about your webhooks subscription. This is based on your preferences for which event(s) you want to subscribe to and how to reference the subscription internally. We’ll use this information in the next steps.
Please fill in the details for a single webhooks subscription. If you plan to create multiple subscriptions, you can go back through this guide for each one separately.
This must be formatted as a comma-separated list with quotes around each event. Example: "entityUpdated","entityDeleted"
Example for just one event: "entityUpdated"
The Identity Cloud user event(s) you’d like to subscribe to. You can follow one or more events per subscription. This will be the event(s) that triggers a notification to your listener endpoint.
Available events are:
"entityCreated" - A new user record is created. It doesn’t matter how the record is created; this can be the result of a new user registration from your website, a new profile creation in Console, or a new profile creation via an internal/backend API call."entityDeleted" - A user record is deleted. It doesn’t matter how the record is deleted; this can be the result of a profile deletion in Console or via an internal/backend API call."entityUpdated" - Any attribute(s) value in a user record is changed. It doesn’t matter how the record is updated; this can be the result of a user profile edit from your website, a profile edit in Console, or a direct change to the record via an internal/backend API call.Example: User Update Subscription
The name you want to give this subscription for internal reference. This name is only seen when you work with the webhooks via the configuration API. If you create multiple webhooks subscriptions, this can help you easily differentiate between them.
Must be between 2 and 200 characters long.