Skip to main content
POST
Identity Match
Compare candidate information against a criminal record subject to determine identity match probability. No authentication required.
Request and response bodies use snake_case field names (candidate_to_verify, is_match, address_match_desc, …). CamelCase (candidateToVerify, isMatch, …) is not accepted and returns HTTP 400.

Request

object
required
Candidate identity to verify (the person being checked).
object
required
Candidate identity found in the criminal record (the person in the record). Same structure as candidate_to_verify.

Response

number
SSN match score (0–1)
string
Description of SSN match result
number
Date of birth match score (0–1)
string
Description of DOB match result
number
Name match score (0–1)
string
Description of name match result (e.g., "Exact Name Match")
number
Address match score (0–1)
string
Description of address match result
number
Overall weighted match score (0–1)
boolean
Whether the match threshold is met. true = positive match.
string
Detailed breakdown of match scores with weights for each component

Code Examples

Copy and modify this JSON payload:
CamelCase / missing required fields (ASP.NET model binding):
Send snake_case keys (candidate_to_verify, candidate_in_record) instead.

Match Scoring

The identity match algorithm uses a weighted scoring system:
Maximum score is 1.00 when SSN, DOB, name, and address all match exactly: (45% x 1.0) + (40% x 1.0) + (10% x 1.0) + (5% x 1.0) = 1.00. Records with SSN + DOB + exact name typically score 0.95+. Without SSN (most common), the practical maximum is 0.90 (name + DOB + address).
  • Evaluate — Main criminal record evaluation endpoint
  • Glossary — Decision values and compliance terminology