Events
This page provides details about specific events of the Corbado Webhook system.
Corbado supports webhooks for the following events:
-
user.created
- sent when a new user is created and confirmed -
user.updated
- sent when a user’s details are updated, including adding or removing an identifier, such as email -
user.deleted
- sent when a user is deleted -
passkey.created
- sent when a new passkey is created -
passkey.deleted
- sent when a passkey is deleted -
passkey-login.completed
- sent when a user successfully logs in using a passkey
Payload structure
JSON payload contains the following fields:
type
- the type of event that occurredmetadata
- metadata about the eventip
- the IP address of the user who triggered the eventos
- the operating system of the user who triggered the eventbrowser
- the browser of the user who triggered the eventcustomHeaders
- custom headers sent with the request, configured by the user
timestamp
- the timestamp when the event occurreddata
- the data associated with the event. Different for each event type
Example:
user.created
user.created
event is sent when a new user is created and confirmed. The data payload contains the following fields:
user
- the user detailsid
- the user IDfullName
- optional full name of the userstatus
- the status of the user
identifiers
- the identifiers associated with the userid
- the identifier IDtype
- the type of identifier, such as emailvalue
- the value of the identifierstatus
- the status of the identifier
user.updated
user.updated
event is sent when a user’s details are updated, including adding or removing an identifier, such as email. The data payload is the same as user.created
and contains the following fields:
user
- the user detailsid
- the user IDfullName
- optional full name of the userstatus
- the status of the user
identifiers
- the identifiers associated with the userid
- the identifier IDtype
- the type of identifier, such as emailvalue
- the value of the identifierstatus
- the status of the identifier
user.deleted
user.deleted
event is sent when a user is deleted. The data payload contains the following fields:
userID
- the user ID of deleted user
passkey.created
passkey.created
event is sent when a new passkey is created. The data payload contains the following fields:
userID
- the user ID of the user who created the passkeycredential
- the credential detailsid
- the credential IDwebAuthnID
- the WebAuthn ID of the userbrowser
- the browser used to create the passkeyos
- the operating system used to create the passkey
passkey.deleted
passkey.deleted
event is sent when a passkey is deleted. The data payload is the same as passkey.created
and contains the following fields:
userID
- the user ID of the user who created the passkeycredential
- the credential detailsid
- the credential IDwebAuthnID
- the WebAuthn ID of the userbrowser
- the browser used to create the passkeyos
- the operating system used to create the passkey
passkey-login.completed
passkey-login.completed
event is sent when a user successfully logs in using a passkey. The data payload is the same as passkey.created
and contains the following fields:
userID
- the user ID of the user who created the passkeycredential
- the credential detailsid
- the credential IDwebAuthnID
- the WebAuthn ID of the userbrowser
- the browser used to create the passkeyos
- the operating system used to create the passkey
Was this page helpful?