SSN Trace API

SSN Trace API for Address & Identity Verification

Verify identity by tracing a Social Security Number. Submit an SSN and receive the full address history, linked phone numbers, name aliases, date of birth, and issuing state — structured JSON, built for compliance, KYC, and background check workflows.

Full address history linked to the SSN with date ranges
Name, aliases, DOB, and SSN issuing state
Linked phone numbers and email addresses
Jurisdiction mapping for follow-on criminal record searches
ID
SSN Trace
ClearCheck Data Engine
Identity Verified
XXX–XX–1319
Issued: Washington
Full Name
John Doe
Name Match
Date of Birth
1987-04-02
Confirmed
Current Address
Las Vegas, NV 89169
Verified
Previous Address
Bellevue, WA 98007
Historical
Deceased Status
Not deceased
Clear
Identity confidence92/100

From an SSN to a Full Identity Record

The SSN Trace API submits a Social Security Number and returns the full identity record associated with it — address history, name aliases, linked contact data, issuing state, and date of birth — in a single structured JSON response.

SSN Validation

Confirm that the Social Security Number is valid and linked to a real person. Returns the issuing state and year the SSN was issued, so you can detect inconsistencies with submitted identity claims.

Address History

Returns the full address history linked to the SSN, each with first and last reported dates. Use the date ranges and jurisdictions to determine which states or counties to search for criminal records.

Identity Verification

Verify submitted name and date of birth against the records linked to the SSN. If firstName and lastName are provided, only matching results are returned — flagging discrepancies automatically.

Alias Discovery

Returns all known name aliases associated with this SSN across historical records. Multiple name variations on the same SSN can indicate identity inconsistencies that require further review.

Linked Contact Data

Returns phone numbers and email addresses found to be associated with this SSN. Pass them to the Phone or Email Lookup API for deeper enrichment and cross-signal identity verification.

Jurisdiction Mapping

Returns county and state combinations from the address history. Use these jurisdictions to scope follow-on searches — such as state criminal records or county court checks — more precisely.

What You Send

The SSN is the only required field. Name fields and address year range are optional filters that narrow the results when provided.

Social Security Number

9-digit SSN in xxx-xx-xxxx format. Required. US Social Security Numbers only.

API Key

Your API key is passed in the request body. Always kept server-side — never exposed in frontend JavaScript code.

Optional Filters

First name, last name, and maxAddressYears filter results to matching records only.

Responsible Use Notice: SSN trace data is sensitive personal information. Use of this API is restricted to permitted compliance, background check, identity verification, and investigative workflows in accordance with applicable law including the FCRA where relevant. Customers are responsible for all compliance obligations.

What You Get Back

Every completed SSN trace returns a structured JSON record with the full identity picture associated with the submitted SSN.

fullNameThe full legal name associated with this SSN in official records. Compare against the applicant's submitted name.
ssnLocationThe US state where this SSN was issued. Mismatch with applicant's stated origin is a red flag worth investigating.
dobDate of birth linked to this SSN. Cross-reference against the applicant's submitted date of birth to detect discrepancies.
addresses[]Full address history with street, city, state, ZIP, county, and first/last reported dates. Used for jurisdiction scoping.
phoneNumbers[]Phone numbers linked to this SSN, with carrier, type, connection status, and reporting dates. Pass to Phone Lookup for enrichment.
emailAddresses[]Email addresses associated with this SSN. Pass to the Email Lookup API for validity, breach exposure, and risk scoring.
aliases[]All name aliases found in historical records for this SSN. Multiple unrecognized aliases can indicate identity inconsistencies.
isDeceasedBoolean. Whether the SSN is linked to a deceased person. Using a deceased person's SSN is a common fraud pattern.
countyStates[]County and state pairs derived from address history. Used to scope follow-on state criminal record and court searches.

Submit, Receive, Poll, Parse

The SSN trace runs through an async enrichment pipeline. Submit the SSN with your API key, hold the job ID, and poll when ready. Your backend keeps processing without waiting.

1

Submit SSN Request

POST the SSN and optional filters with your API key and methodName "ssn_trace". US SSNs only in xxx-xx-xxxx format.

2

Receive Job ID

The API responds immediately with a numeric job ID and status "progress". No waiting required at this step.

3

Poll for Completion

Query the monitor endpoint using the job ID. When status changes to "completed", the full identity record is ready.

4

Use the Record

Parse addresses for jurisdiction scoping, compare name and DOB, check isDeceased, and pass contact data to further enrichment APIs.

How to Make an SSN Trace Call

Send one POST request with the SSN and your API key. Get a job ID back straight away — no waiting. Poll once to pick up the full identity record when it's ready.

Set methodName to ssn_trace in the request body. Optionally include firstName, lastName, and maxAddressYears to filter results to matching records only.

API key passed in request body — always stays server-side
Non-blocking — submit and move on, collect results when ready
US Social Security Numbers only — format xxx-xx-xxxx
Full address history with county codes for jurisdiction scoping

Docs are currently on our existing portal and will move to the ClearCheck Data portal soon.

POST /api/developer/irbis_background_checks JSON
// 1. Submit SSN trace
POST /api/developer/irbis_background_checks
Content-Type: application/json
{
  "key":          "YOUR_API_KEY",
  "methodName": "ssn_trace",
  "ssn":          "123-45-6789",
  "firstName":   "John",
  "lastName":    "Doe",
  "lookupId":   46
}

// 2. Initial response
{
  "id":     8821047,
  "status": "progress"
}

// 3. Poll for result
GET /api/request-monitor/api-usage/8821047

// 4. Completed response
{
  "fullName":     "John Doe",
  "ssnLocation": "Washington",
  "dob":         "1987-04-02",
  "isDeceased":  false,
  "addresses":   [...]
}

Who Uses SSN Trace and Why

SSN trace is a foundational step in identity verification and background check workflows — giving organizations the address history and identity record they need before running further searches.

KYC & Onboarding

Verify that the SSN, name, and date of birth submitted during onboarding are consistent with official records. Discrepancies or deceased-status flags trigger additional verification steps before account approval.

Fraud Prevention

Detect synthetic identity fraud — where fraudsters combine real SSNs with false names — by comparing the name returned by the trace against the applicant's submitted name. A deceased SSN is an immediate hard block.

Risk Orchestration

Feed SSN trace results into your risk rules engine. Use address history, alias count, and name match status to automatically score and route applicants into the right decision queue.

OSINT & Investigations

Use the returned address history and jurisdiction list as the starting point for deeper investigation. County and state pairs from the trace directly scope which criminal records and courts to search next.

E-commerce Verification

For high-value transactions requiring identity confirmation, an SSN trace provides a structured identity record that goes beyond email and phone signals — including full name, DOB, and address match.

Compliance Screening

For regulated industries requiring identity verification before service delivery, SSN trace provides the structured record needed to document that identity was confirmed against official government-issued data.

Frequently Asked Questions

No. The SSN Trace API is available for US Social Security Numbers only. Social Security numbers are issued exclusively by the US Social Security Administration and the trace data is sourced from US data providers. If you need identity verification for non-US individuals, please contact sales to discuss available international enrichment options.
SSN trace data is sensitive personal information subject to applicable US federal and state privacy laws. Use of this API is restricted to permitted compliance, background check, identity verification, and investigative workflows. Customers are responsible for ensuring their use complies with all applicable laws including the Fair Credit Reporting Act (FCRA) where relevant, state privacy regulations, and their own data handling obligations.
The API accepts SSNs in the standard xxx-xx-xxxx format with dashes — for example, 123-45-6789. The SSN field is the only required parameter. All other fields (firstName, lastName, maxAddressYears) are optional and act as filters to narrow the returned results to records that match the additional fields you provide.
When you include firstName and lastName in the request, the API filters results to only return records where both the SSN and the provided name match. This makes the trace more precise for verification workflows. If you submit an SSN without name fields, all names associated with that SSN are returned — which is useful for discovering aliases or auditing identity consistency.
Each address record in the returned addresses array includes the full street address, city, state, county, ZIP code, and coordinates, as well as firstReportedDate and lastReportedDate. The countyStates array summarizes the county and state pairs — these are the jurisdictions most commonly used to scope follow-on criminal record searches. Use maxAddressYears to filter out historical addresses older than a specified number of years.
When isDeceased returns true, the SSN is linked to a person who is recorded as deceased. Using a deceased person's Social Security Number is one of the most common forms of synthetic identity fraud and identity theft. An isDeceased = true result should trigger immediate escalation, additional verification, or automatic rejection depending on your workflow rules.