Skip to main content

Soft ID Verification

Soft ID Verification (a.k.a. Soft KYC, eIDV, 2x2 verification) is a feature that enables cross-checking data against official/registry sources. The feature functionality is simple and straightforward: all you need to do is to provide the individual personal details and retrieve the results if it match or not.

Generate requests

The request must contain basic auth headers where username is API key and password is API secret. Two main endpoints are used to list/retrieve and perform Soft ID Verification.

Perform Soft ID verification check

Examples

Send a HTTP POST request to: https://ivs.idenfy.com/api/v2/registry-center-checks/

Possible values:

JSON keyRequiredTypeExplanation/Possible values
firstNameYesStringFirst name of the person.
lastNameYesStringLast name of the person.
stateYesString- Possible values: AL, AZ, AR, CA, CO, CT, DE, DC, FL, GA, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY, AK, HI.
databaseYesStringDatabase type, provide US_1 for this request.
dobNoString- Format: YYYY-MM-DD;
- Lowest value: 1900-01-02.
middleNameNoStringMiddle name of the person.
yobNoInteger- Possible values: [1901..2050].
genderNoString- Possible values: MALE/FEMALE.
addressNoStringAddress of the person.
cityNoStringCity of the person.
zipNoStringZip code of the area, numbers allowed only.
phoneNoStringFormat should include country, area and telephone number, e.g.: "+1 (416) 555-5678".
maritalStatusNoString- Possible values: MARRIED/NOT_MARRIED.
{
"firstName": "John",
"lastName": "Smith",
"state": "CA",
"database": "US_1",
"middleName": "Adrian",
"yob": 1980,
"gender": "MALE",
"city": "San Jose",
"zip": "95128"
}

List/retrieve Soft ID verification checks

To retrieve all performed Soft ID verification checks, send GET request at: https://ivs.idenfy.com/api/v2/registry-center-checks/

Response example

Toggle to open
[
{
"id": "13c7c069-d4d8-405b-a442-3fe483068ca5",
"firstName": "Jay Alan",
"lastName": "Neander",
"state": "IL",
"middleName": null,
"dob": "1981-08-31",
"yob": null,
"gender": "MALE",
"address": null,
"city": "Chocago",
"zip": "60646",
"phone": null,
"maritalStatus": "MARRIED",
"firstNameStatus": "NO_MATCH",
"lastNameStatus": "NO_MATCH",
"stateStatus": "NO_MATCH",
"middleNameStatus": null,
"dobStatus": "NO_MATCH",
"yobStatus": null,
"genderStatus": "NO_MATCH",
"addressStatus": null,
"cityStatus": "NO_MATCH",
"zipStatus": "NO_MATCH",
"phoneStatus": null,
"maritalStatusStatus": "NO_DATA",
"database": "US_1"
},
{
"id": "83cb0614-ff58-41e6-afac-6f24b8ff0072",
"firstName": "Jay Adomas",
"lastName": "NEander",
"state": "IL",
"middleName": null,
"dob": null,
"yob": null,
"address": null,
"city": null,
"zip": null,
"phone": null,
"idNum": null,
"firstNameStatus": "MATCH",
"lastNameStatus": "MATCH",
"middleNameStatus": null,
"dobStatus": null,
"yobStatus": null,
"addressStatus": null,
"cityStatus": null,
"zipStatus": null,
"phoneStatus": null,
"idNumStatus": null,
"database": "US_4"
},
{
"id": "a86aff0a-95a2-46a3-a9fa-27fabfef37f6",
"firstName": "Thomas R",
"lastName": "Ahern",
"middleName": null,
"dob": "1979-02-24",
"yob": 1979,
"address1": null,
"address2": null,
"city": null,
"state": "NY",
"zip": null,
"idNum": null,
"phone": null,
"email": null,
"firstNameStatus": "MATCH",
"lastNameStatus": "MATCH",
"middleNameStatus": null,
"dobStatus": "MATCH",
"yobStatus": null,
"address1Status": null,
"address2Status": null,
"cityStatus": null,
"stateStatus": "MATCH",
"zipStatus": null,
"idNumStatus": null,
"phoneStatus": null,
"emailStatus": null,
"database": "US_15"
}
]

Results

note

Please note that only fields with a corresponding *Status suffix are verified against the database, and their values indicate the outcome of this verification. Fields without a *Status suffix are informational and reflect the data provided in the request.

The results are based on each value and there are no overall results *Status: Appended to the name of each request information field (e.g., firstNameStatus, lastNameStatus, maritalStatusStatus), these keys indicate the verification status of the corresponding data. Here are the possible results:

  • Match - More than 85% Match.
  • Partial Match - Less than 85% but greater than 50%.
  • No Match - Less than 50%.
  • Invalid - invalid format information provided.
  • No Input - The requested input is blank data.
  • No Data - No Match data was obtained from the source.
  • null - No input.