Get Bot Verdict
Fetch bot verdict for a user session token
Response Format
The API returns detailed information about the request, including:- Verdict - Whether the request should be allowed (
can_pass: true/false) and whether the token had already been redeemed (redeemed: true/false) - Device information - Browser details, fingerprint, user agent
- IP analysis - Location, threat indicators, proxy/VPN detection
- Session data - Timing and behavioral analysis
Token Redemption
Tokens can be verified more than once — replay does not produce an error. Useverdict.redeemed to detect it:
verdict.redeemed: false— first time this token has been verifiedverdict.redeemed: true— this token was already verified by a previous/verifycall
verdict.redeemed is true.
Testing
For local development, use test action IDs that return predictable results without consuming API credits:- Success:
t/FFFFFFFFFFFFF/111111111(always returnscan_pass: true) - Failure:
t/FFFFFFFFFFFFF/000000000(always returnscan_pass: false)
Body
Verdict request with session token and optional user identification
Your Deflect API Key
Your Deflect Action ID
The user session token from the protected endpoint.
Optional user identifier for multi-accounting detection. Highly recommended to include.
Optional user email address. Response will include email risk assessment.
Optional user phone number in E.164 format. Response will include phone validation.
Response
Successful response
Echo of the user identifier passed in the request.
Bot detection score from 0 (bot) to 100 (human).
Included when an email address is passed in the request.
Included when a phone number is passed in the request.
Bot rules and access rules that matched this request.
Multi-accounting detection results. Requires a user id in the request.