Authenticator challenge events
Sent so you can deliver a challenge through your own provider. Synchronous: a non-2xx response fails the challenge.Authenticator events
Fired when an authenticator is added to a user, updated, or removed. By default, only changes the user makes send events, plusauthenticator.expired. You can opt in to changes made in the Authsignal Portal or through the Server API.
These can be used to send custom notifications so that users are aware of changes to the factors protecting their account, and to synchronise user details with third-party systems such as CRMs.
Asynchronous, with up to 3 retries.
Action verification events
Sent during action evaluation. These can be used to trigger additional blocking checks while a challenge is being verified. Synchronous: a non-2xx response blocks the outcome.Log events
Audit records for actions and challenges, delivered in batches for SIEM or data-lake forwarding. Asynchronous, batched, at-least-once.Envelope schema
Every webhook delivery shares a common envelope. Event-specific fields live underdata (or record, for log events).

