Skip to main content

Social Security Number Verification API

This document highlights the details of the Social Security Number Verification API.

API Description

Objective

The SSN Verification API checks the information on a Social Security Number (SSN) and confirms if it matches the official data maintained by the issuing authority. The API confirms SSN ownership, detect mismatches or invalid cases, and support fraud prevention and compliance checks.

Info
  • A Social Security number (SSN) is a unique nine-digit identifier for U.S. citizens, permanent residents, and eligible workers, issued by the Social Security Administration (SSA).
  • Social Security Numbers issued by U.S. jurisdictions are commonly used for identity verification but can be counterfeit or altered. Verifying their authenticity is essential for accurate identification.
InputOutput
User details including:
  • First name
  • Last name
  • SSN
The verification results indicate whether the user's name and SSN fully match, partially match, or do not match the official records, confirming if the SSN is valid, active, and correctly associated.

API URL

https://usa.thomas.hyperverge.co/v1/ssnVerification

API Endpoint

ssnVerification

Overview

The Social Security Number Verification API is RESTful and uses standard HTTP verbs and status codes. The requests are in form-data format and responses are in JSON format.

Authentication

You need a unique pair of application ID ( appId ) and application key (appKey) from HyperVerge to verify your identity for accessing the API.

ParameterMandatory or OptionalDescriptionAllowed Values
content-type MandatoryThis parameter defines the media type for the request payloadapplication/json
appId MandatoryThe application identifier shared by HyperVerge. You can find the details in the dashboard's credentials tab.This should be a unique value.
appKey MandatoryThe application key shared by HyperVerge. You can find the details in the dashboard's credentials tab.This should be a unique value.
transactionIdMandatoryA unique identifier for tracking a user journeyThis should be both unique and easily associated with the user's journey in your application(s)

API Request Details

Method - POST

Headers

ParameterMandatory or OptionalDescriptionValid Values
content-typeMandatoryThis parameter defines the media type for the request payloadapplication/json
appIdMandatoryThe application ID shared by HyperVergeNot Applicable - this is a unique value
appKeyMandatoryThe application key shared by HyperVergeNot Applicable - this is a unique value
transactionIdOptionalThe unique ID for the customer journeyNot Applicable

Inputs

The following table lists the parameters required for the Social Security Number Verification API's request body:

ParameterMandatory or OptionalDescriptionAllowed ValuesDefault Value
firstNameMandatoryThe first name of the userNot ApplicableNot Applicable
lastNameMandatoryThe last name of the userNot ApplicableNot Applicable
ssnMandatoryThe SSN of the userA nine-digit number formatted as XXX-XX-XXXX. For example, 123-45-6789Not Applicable

Request

The following code snippet demonstrates a standard curl request for the Social Security Number Verification API:

curl --location --request POST 'https://usa.thomas.hyperverge.co/v1/ssnVerification' \
--header 'Content-Type: application/json' \
--header 'appId: <Enter_the_HyperVerge_appId>' \
--header 'appKey: <Enter_the_HyperVerge_appKey>' \
--header 'transactionId: <Enter_the_HyperVerge_transactionID>' \
--data '{
"firstName": "<Enter_the_first_name>",
"lastName": "<Enter_the_last_name>",
"ssn": "<Enter_the_SSN>"
}'

Success Responses

The following code snippets demonstrate success responses from the Social Security Number Verification API:

{
"status": "success",
"statusCode": "200",
"result": {
"details": {
"ssnMatch": "fullMatch"
},
"summary": {
"action": "pass",
"details": []
}
}
}

Success Response Details

The following table outlines the details of the success response from the Social Security Number Verification API:

ParameterTypeDescription
statusstringIndicates the status of the request
statusCodestringThe HTTP status code for the request
resultobjectThe object containing the result details
detailsobjectContains details about the SSN match result
ssnMatchstringIndicates the verification result for the SSN and name combination. Returns "fullMatch" for complete matches, "partialMatch" for partial matches, "noMatch" for no matches, "deceased" for SSNs that are no longer active, "invalidFormat" for SSNs with incorrect length or format, and "notFound" when the SSN is valid but the name doesn't match the provided details
summaryobjectProvides a summary of the verification result
actionstringRepresents the action based on the verification result, such as pass or fail
detailsarrayAn array containing additional details about the summary, if available

Error Responses

The following are the error responses for the Social Security Number Verification API:

{
"status": "failure",
"statusCode": "400",
"error": "ssn is required"
}
{
"message": "Missing/Invalid credentials",
"statusCode": 401,
"status": "failure"
}

Error Response Details

A failure or error response from the API contains a failure status with a relevant status code and error message. The following table lists all error responses.


Status CodeError MessageError Description
400ssn is requiredThe SSN field is missing in the request body
400firstName is requiredThe first name is empty in the request body
400lastName is requiredThe last name is empty in the request body
400Please provide valid firstNameThe first name contains invalid characters
400Please provide valid lastNameThe last name contains invalid characters
400Please provide valid SSNThe SSN contains special characters or has an invalid format
401Missing/Invalid credentialsThe request is either missing the mandatory appId and appKey combination or has invalid values
500Internal Server ErrorPlease check the request headers or contact the HyperVerge team for resolution
Was this helpful?
Ask AIBeta
Hi! How can I help?
Ask me anything about HyperVerge products, APIs, and SDKs.
Try asking: