Skip to main content
Identity Intelligence extends Email Intelligence with deeper identity analysis. When enabled, Verisoul pulls in additional data sources to build a picture of the person behind an email address — their online presence, connected identities, and whether provided claims (name, phone, country) match the data. This is particularly valuable for:
  • Account creation — verify that the person signing up is real and matches the information they provided
  • High-value transactions — add an extra layer of identity confidence before approving a purchase or transfer
  • KYC/onboarding workflows — cross-reference claims against independent data sources

​
How to Enable It

Set identity_intelligence: true in your request. In batch mode, this applies to all emails in the batch. Single email: 
{
  "email": "john.doe@example.com",
  "identity_intelligence": true,
  "claims": {
    "name": { "first": "John", "last": "Doe" },
    "phone": "+15550109988",
    "country": "US"
  }
}
Batch: 
{
  "emails": [
    {
      "email": "john.doe@example.com",
      "claims": {
        "name": { "first": "John", "last": "Doe" },
        "country": "US"
      }
    },
    {
      "email": "jane.smith@company.com",
      "claims": {
        "name": { "first": "Jane", "last": "Smith" },
        "phone": "+14155551234"
      }
    }
  ],
  "identity_intelligence": true
}
In batch mode, each email has its own claims, so you can verify different identities in a single request.

​
Claims

Claims are pieces of information your customer has provided that you want to verify against Verisoul’s identity data. All claims are optional.
ClaimTypeDescription
name.firststringCustomer’s first name
name.laststringCustomer’s last name
phonestringPhone number (E.164 format recommended)
countrystringTwo-letter country code (ISO 3166-1 alpha-2)
When claims are provided, Verisoul matches them against identity data linked to the email and returns match results.

​
What You Get Back

When identity_intelligence is enabled, the webhook payload includes an additional identity_intelligence section inside data.result: 
{
  "identity_intelligence": {
    "match_risk_score": -0.4,
    "online_accounts": ["google", "linkedin", "github", "facebook", "instagram"],
    "connected_names": ["John Doe"],
    "connected_phones": ["+1555*******"],
    "claim_matches": {
      "name": "match",
      "phone": "skipped",
      "country": "match"
    }
  }
}

​
Fields

FieldTypeDescription
match_risk_scorenumberComposite identity risk score from -1 (verified identity) to 1 (ghost / no identity footprint). Factors in online presence, claim matches, and identity consistency.
online_accountsstring[]Platforms where the email is registered (e.g., google, facebook, linkedin, twitter, github). A rich online presence is a strong trust signal.
connected_namesstring[]Names associated with this email across data sources.
connected_phonesstring[]Phone numbers linked to this email.
claim_matchesobjectResults of matching each submitted claim against identity data.

​
Claim Match Values

Each claim is matched independently and returns one of:
ValueMeaning
matchThe claim matches identity data linked to the email
partial_matchPartial overlap (e.g., first name matches but last name differs)
no_matchThe claim does not match any known identity data
skippedNo claim was provided for this field, or identity data was unavailable

​
How It Affects the Score

When Identity Intelligence is enabled, the identity data directly influences the overall risk_score:
  • Identity Match — a strong name/phone match pushes the score toward trust, while mismatches or ghost identities push toward risk.
  • Online presence — emails registered on many legitimate platforms (Google, LinkedIn, Facebook, etc.) are more likely to belong to real people, which is a strong trust signal.
A verified identity match can pull an otherwise neutral email into the “trusted” range, while a complete identity mismatch can significantly increase risk.

​
Without Identity Intelligence

If identity_intelligence is not set or is false, the webhook payload will not include the identity_intelligence section. Identity-related signals will not factor into the overall risk score. Email Intelligence still provides full risk scoring, deliverability, domain classification, and breach intelligence without Identity Intelligence enabled.