SSN Trace V1
Introduction
Due Diligence is one of the first checks that is done for background verification of any gig worker, blue-collar worker, and several other working classes. The sources for such checks can be very diverse and include Federal and State criminal databases, motor vehicle report checks, civil court checks, etc. Signzy has created a global NDD product that has an exhaustive list of sources through which an employer, or any entity can be sure that the person they are going to work with is a trustworthy individual.
As a first step, we have already National Criminal Checks, PEP, Adverse Media & Watchlists checks API required for background verification of the person. Now, the SSN Trace API is used to verify the user's identity and and details associated with the user.
Social Security trace searches are performed with every background check to indicate the name and address history of an applicant. SSN trace will also confirm whether the Social Security number is valid and matches the candidate’s name and address history. SSN trace will give insight to which jurisdictions should be searched.  Please note that this is not an alternative of SSN Verification Service.
The search is typically the first step and often combined with a NatCrim search to confirm or to indicate potential criminal record history. This information is used as an indicator of potential risk a candidate could pose to an organization.
By searching an SSN, we will provide the name(s), address(es), and phone number(s) associated with that identification number from a variety of sources.
API Applications
Some important business areas where the SSN Trace API is very helpful are:
Fraud Detection:
The API can help detect potential fraud by comparing the provided SSN against databases to identify inconsistencies or discrepancies.
Background Checks:
Employers and organizations can use SSN traces for background checks during the hiring process to validate a candidate's identity and history.
Compliance:
In regulated industries such as finance and healthcare, using SSN traces can help comply with legal and regulatory requirements for customer due diligence and Know Your Customer (KYC) procedures.
Customer Onboarding:
Businesses can streamline customer onboarding processes by using SSN traces to quickly verify identity information provided by customers.
Reduced Errors:
Manual data entry errors can occur when collecting personal information. An SSN trace API can minimize errors by automating the retrieval of accurate details associated with an SSN.
Enhanced Data Accuracy:
The API can provide up-to-date and accurate information about individuals, improving the quality of data in customer databases.
Risk Assessment:
Financial institutions and lending companies can use SSN traces as part of their risk assessment processes to determine an applicant's creditworthiness.
Personalization:
For marketing and customer service purposes, having accurate customer information can enable personalized interactions and communications.
Efficiency:
Instead of manually verifying SSN information, the API allows for quick and automated data retrieval.
Note :-
The SSN (Social Security Number) Trace is intended to verify the personal identifying information associated with a specific individual's Social Security number.
An SSN trace supplies details about names and addresses associated with a specific Social Security number and can offer insights into address history.
However, it’s important to note that SSN traces do not confirm the authenticity of the SSN or validate that it belongs to the individual providing it. The accuracy of the information in the trace depends on the reliability of the reporting agencies.
Sample cURL
curl --location 'https://api.signzy.us/api/v3/us-api/ssn-trace-v1' \
--header 'Content-Type: application/json' \
--header 'Authorization: *****' \
--data '{
"socialSecurityNumber": "",
"firstName": "",
"middleName": "",
"lastName": "",
"dateOfBirth": ""
}'Request Body Parameters

Parameter | Data Type | Required | Description |
|---|---|---|---|
socialSecurityNumber | string | Yes | 9-digit SSN. Rejects area 000, 666, 9xx, group 00, serial 0000. |
firstName | string | No | Max 100 characters. Letters, spaces, -, ', . only. |
middleName | string | No | Max 100 characters. Same validation as firstName. |
lastName | string | No | Max 100 characters. Same validation as firstName. |
dateOfBirth | string (YYYY-MM-DD) | No | Valid calendar date, year ≥ 1900. Converted to vendor format (MM/DD/YYYY). |
Sample Response
{
"result": {
"addressHistory": [
{
"socialSecurityNumber": "",
"dateOfBirth": "1",
"currentAge": "36",
"addressLine1": "",
"addressLine2": "Aurora, IL 60502",
"countyName": "Kane",
"associatedNames": [""],
"contactNumbers": [""],
"firstSeenOn": "2021-12-08",
"lastSeenOn": "2026-06-01"
},
{
"socialSecurityNumber": "",
"dateOfBirth": "",
"currentAge": "36",
"addressLine1": "",
"addressLine2": "",
"countyName": "Dupage",
"associatedNames": ["Saurin Parikh"],
"contactNumbers": [""],
"firstSeenOn": "",
"lastSeenOn": "2023-02-06"
}
]
},
"reason": "Request Successful",
"code": "S001"
}
Response Body parameters

Parameter | Data Type | Required | Description |
|---|---|---|---|
socialSecurityNumber | string | Yes | SSN associated with the address record. |
dateOfBirth | string (YYYY-MM-DD) | Yes | DOB on the record (normalized). |
currentAge | string | Yes | Current age (default ""). |
addressLine1 | string | Yes | Street address line 1. |
addressLine2 | string | Yes | Street address line 2. |
countyName | string | Yes | County name. |
associatedNames | array | Yes | Names associated with the address. |
contactNumbers | array | Yes | Phone numbers associated with the address. |
firstSeenOn | string (YYYY-MM-DD) | Yes | First reported date (normalized). |
lastSeenOn | string (YYYY-MM-DD) | Yes | Last reported date (normalized). |
Sample error
{
"result": {},
"reason": "Bad Request: socialSecurityNumber can not be empty",
"code": "E001"
}Error Response Parameters
HTTP Status Code | Error Code | Description |
|---|---|---|
400 | E001 | Bad Request |
401 | E101 | Unauthorized Access |
403 | E201 | Forbidden |
404 | E301 | Data Not Found |
409 | E401 | Upstream error |
429 | E501 | Rate Limit Exceeded |
500 | E601 | Internal Server Error |
503 | E701 | Service Unavailable |
504 | E801 | Timeout |

Getting help
Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.
You can reach out to us at [email protected]. We strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively.
We value your feedback and are committed to making your experience smooth and enjoyable. Our team is dedicated to assisting you with any needs you may have. Thank you for choosing our services. We look forward to helping you!