Get a phone verification
Retrieve everything Prelude recorded for one phone verification: its outcome and the device, network and anti-fraud context it was created in, the chronological timeline of every message attempt and code check, and the anti-fraud signals you forwarded.
The identifier is the id returned by Create or retry a verification or the verification_id of the verification webhooks. Both lifecycle and signals are optional: a verification can resolve with its top-level fields alone.
lifecycle and signals are both optional: a verification can resolve with its top-level fields alone.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The verification identifier.
"vrf_01jc0t6fwwfgfsq1md24mhyztj"
Response
OK
A verification and everything Prelude recorded about it.
The verification identifier.
"vrf_01jc0t6fwwfgfsq1md24mhyztj"
The E.164 phone number the verification targeted.
"+33612345678"
The outcome of the verification.
converted- The end user submitted a valid code.not_converted- The verification expired without a valid code.pending_check- A code was delivered and Prelude is still waiting for a check.sent- A code was sent and the verification window is still open.challenged- The verification was restricted to non-SMS and non-voice channels.suspected_fraud- The anti-fraud system blocked the verification.in_blocklist- The phone number is on the configured block list.invalid_line- The phone number is not a valid line type.invalid_number- The phone number is not a valid number.rate_limited- The verification was refused by a rate limit.expired_signals- The SDK signals were collected too long before the request.shadowed- The anti-fraud system flagged the verification without blocking it.
converted, not_converted, pending_check, sent, challenged, suspected_fraud, in_blocklist, invalid_line, invalid_number, rate_limited, expired_signals, shadowed Platform of the end-user device, when known.
android, ios, ipados, tvos, web Model of the end-user device, when known.
"iPhone15,2"
Version of your application, when known.
IP address the verification was created from.
ISO 3166-1 alpha-2 region of the phone number.
"FR"
ISO 3166-1 alpha-2 region of the caller's IP address.
"FR"
Distance between the phone number region and the IP location.
The end user's mobile network.
Why the anti-fraud system blocked the verification. Empty unless it did.
behavioral_pattern- The phone number past behavior during verification flows exhibits suspicious patterns.device_attribute- The end-user device reported attributes associated with fraud or emulation.fraud_database- The phone number appears in a fraud database.location_discrepancy- The phone number region and the observed location disagree.missing_signals- The verification expected Prelude SDK signals and none arrived.network_fingerprint- The network fingerprint matches known fraudulent traffic.poor_conversion_history- The phone number rarely completes the verifications it starts.prefix_concentration- The phone number is part of a range known to be associated with suspicious activity patterns.repeated_number- The phone number was used far more often than normal traffic would explain.suspected_request_tampering- The SDK signals were altered or expired between collection and use.suspicious_ip_address- The originating IP address is associated with suspicious activity.temporary_phone_number- The phone number is known to be a temporary or disposable number.
behavioral_pattern, device_attribute, fraud_database, location_discrepancy, missing_signals, network_fingerprint, poor_conversion_history, prefix_concentration, repeated_number, suspected_request_tampering, suspicious_ip_address, temporary_phone_number Whether the phone number was allow-listed, block-listed, or sandboxed at verification time.
allow_listed, block_listed, sandboxed Whether the phone number is currently allow-listed, block-listed, or sandboxed.
allow_listed, block_listed, sandboxed Whether the SDK signals integrity check passed.
valid, invalid The correlation identifier you supplied when creating the verification.
The template used for this verification.
Chronological timeline of the verification: creation, message attempts with delivery events, code checks and signals reception. Omitted when Prelude holds no timeline for the verification.
The anti-fraud signals you forwarded when creating the verification.