Skip to main content

Onsite Integration

In onsite verification, Shufti will directly interact with the end user to collect the required proofs for verification purposes.

Parameters and Description​

ParametersDescription
emailRequired: No
Type: email
Maximum: 128 characters
Allowed Characters: Kindly ensure that email addresses adhere to the standard conventions, including valid characters such as letters, numbers, and symbols like '@' and '.'.
validate_emailRequired: No
Type: string
Accepted Values: 0, 1
Default Value: 1
After verifying the email address and enabling the key, it undergoes a thorough validation against pre-set fraud prevention criteria to detect any fraudulent or suspicious activity, ensuring the email is not only valid but also secure and free from malicious associations.
email_intelligenceRequired: No
Type: Boolean
Minimum: 6 characters
Maximum: 128 characters
Accepted Value: Email Address
This field represents the email score of the end-user. It is used as a part of Shufti’s email verification process. The system checks the email for potential fraud indicators, such as disposable domains or high-risk registrars. This helps to ensure the validity and authenticity of the email address provided by the end-user.

Note: Any score above 7.0 will be considered as a valid email address. A score below 7.0 can be marked as risky or invalid depending upon the type of risk signals detected.

Run in Postman

email-verification-service-sample-object-empty-email
{
  "email_verify" : {
      "email" : ""
  }
}
caution

Shufti requires the end-user to furnish the email address if absent in both the general request and email_verify objects. The email in the general request takes precedence if the email_verify object is empty. It's imperative that email addresses in both objects align precisely for request processing.

email-verification-service-sample-object-filled-email
{
  "email_verify" : {
      "email" : "[email protected]"
  }
}