Skip to main content
POST
Predict outcome
Call Predict at signup for a real-time legitimate or suspicious outcome on the identifier the user provides. Set target.type to phone_number or email_address with the corresponding value. Predict is scoring-only. It evaluates forwarded signals (IP, device, JA4, and more) and does not imply that you sent a message, started a verification step, or triggered any other side effect. It does not update long-lived abuse counters by itself. If you use Feedback for your own verification funnel, call Predict before verification.started on the same target and reuse metadata.correlation_id on both requests. Prelude links the feedback to the stored prediction so auth-start counters in the Watch pool receive those signals. Feedback alone without a prior predict only updates attempt-rate counters. You can use Predict without Events or Feedback, or combine all three. See Introduction — How the pieces fit together.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
target
object
required

The signup identifier to score — a phone number or email address.

signals
object

The signals used for anti-fraud. For more details, refer to Signals.

dispatch_id
string

The identifier of the dispatch that came from the front-end SDK.

Required string length: 36
Example:

"123e4567-e89b-12d3-a456-426614174000"

metadata
object

The metadata for this prediction.

Response

OK

id
string
required

The prediction identifier.

Example:

"prd_01jc0t6fwwfgfsq1md24mhyztj"

prediction
enum<string>
required

The prediction outcome.

Available options:
legitimate,
suspicious
request_id
string
required

A string that identifies this specific request. Report it back to us to help us diagnose your issues.

Example:

"3d19215e-2991-4a05-a41a-527314e6ff6a"

risk_factors
enum<string>[]

The risk factors that contributed to the suspicious prediction. Only present when prediction is "suspicious" and the anti-fraud system detected specific risk signals.

  • behavioral_pattern - The phone number past behavior during verification flows exhibits suspicious patterns.
  • device_attribute - The device exhibits characteristics associated with suspicious activity patterns.
  • fraud_database - The phone number has been flagged as suspicious in one or more of our fraud databases.
  • location_discrepancy - The phone number prefix and IP address discrepancy indicates potential fraud.
  • network_fingerprint - The network connection exhibits characteristics associated with suspicious activity patterns.
  • poor_conversion_history - The phone number has a history of poorly converting to a verified phone number.
  • prefix_concentration - The phone number is part of a range known to be associated with suspicious activity patterns.
  • suspected_request_tampering - The SDK signature is invalid and the request is considered to be tampered with.
  • suspicious_ip_address - The IP address is deemed to be associated with suspicious activity patterns.
  • temporary_phone_number - The phone number is known to be a temporary or disposable number.
Available options:
behavioral_pattern,
device_attribute,
fraud_database,
location_discrepancy,
network_fingerprint,
poor_conversion_history,
prefix_concentration,
suspected_request_tampering,
suspicious_ip_address,
temporary_phone_number
Example: