Detect suspicious emails for trust & safety and fraud prevention use cases
ALLOW, BLOCK, or CHALLENGE) and a more granular risk_score.
You can also check the address_information and domain_information fields for more information about the email address and email domain.
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Request type
The email address to check.
Successful response
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue.
Information about the email address.
Information about the email domain.
The suggested action based on the attributes of the email address. The available actions are:
ALLOW - This email is most likely safe to send to and not fraudulent.BLOCK - This email is invalid or exhibits signs of fraud. We recommend blocking the end user.CHALLENGE - This email has some potentially fraudulent attributes. We recommend increased friction such as 2FA or other forms of extended user verification before allowing the privileged action to proceed.ALLOW, CHALLENGE, BLOCK A score from 0 to 100 indicating how risky the email is. 100 is the most risky.
The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.