Request body
Send at least one ofemail, phone, client.ip or device_token.
The business flow:
signup or login. The Risk Platform runs the policy mapped to this flow.Your correlation key for this check, up to 128 characters. Generate it on your server. A retry with the same event ID and the same inputs returns the existing check; the same event ID with different inputs returns
409 event_conflict. Strongly recommended.The device token from the
x-abstract-device-token header of the browser request. Opaque and single-use; don’t parse it. See Device tokens.Small, non-sensitive metadata of your own, such as the signup surface. Never put passwords, cookies, session data or authorization headers here.
Returns a fixed test response instead of running a live check. Test checks aren’t stored, and test responses carry the
X-Protection-Test-Mode: true header.Response
The unique ID of this check. Use it to find the check in the dashboard and to report outcomes.
How complete the evidence was:
confidence (verified, partial or unverifiable) and gaps, the fields a rule needed but couldn’t resolve.Request quality:
device (token_present, token_valid, reason), ip_source, ip_trusted, and the velocity assessment (status of none, watch or high, contributors, reason).The email signal used by the check, from Email Intelligence.
The phone signal used by the check, from Phone Intelligence.
The IP signal used by the check, from IP Intelligence.
Compatibility fields
Responses also includecall_id, run_id, verdict, risk_level, decision_phase, score, policy_applied, policy_version, data_gaps and check_confidence. They are kept for older integrations and are deprecated. Use check_id, recommendation, policy and data_quality instead.
Errors
See Errors for the error format.