These webhooks are asynchronous and delivered in batches of up to 500 events, after your tenant’s challenge token duration (typically 15 minutes). Delivery is at-least-once, so de-duplicate using the envelopeDocumentation Index
Fetch the complete documentation index at: https://docs.authsignal.com/llms.txt
Use this file to discover all available pages before exploring further.
id.
Configure the webhook URL for log events in tenant settings.
Batch delivery format
Payload
The ID of the tenant that the action occurred within.
The ID of the user that the action was triggered by.
The action being evaluated (e.g.
login, withdrawal).Unique per action instance.
When the action was first evaluated.
When the action record was last updated.
Final action state. One of
ALLOW, BLOCK, CHALLENGE_REQUIRED, CHALLENGE_SUCCEEDED, CHALLENGE_FAILED, REVIEW_REQUIRED.When state last changed.
The rule engine decision. One of
ALLOW, BLOCK, CHALLENGE, REVIEW. Immutable for the lifetime of the action.The method the user actually used to complete a challenge, if any (e.g.
EMAIL_OTP, PASSKEY, SMS, AUTHENTICATOR_APP).The set of methods the user was offered for this challenge. Omitted if empty.
Rules that fired during evaluation. Omitted if none.
The rule that drove the outcome, when multiple rules fired.
IP address of the request that initiated the action.
Country resolved from the IP.
Email on file for the user at the time of the action.
Phone number on file for the user at the time of the action.
Opaque identifier for the device that initiated the action.
Verification methods the user had enrolled at the time of the action.
Custom key/value data supplied by your application. Omitted if empty.

