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 a user adds, updates, or removes an authenticator. 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).
Event metadata
string
required
A unique identifier for the event.
string
required
The source of the event. This is always
https://authsignal.com.string
required
The time the event was created in ISO 8601 format.
string
required
The type of the event. Each type has a different schema for the
data field.string
required
The version of the event.
string
required
The ID of the tenant that the event is intended for.
object
required
The event-specific data. See below for the schema of the
data field for each event type.