eIDV Advance API

introduction the eidv advance api enables real time electronic identity verification (eidv) of individual consumers in the u s using a combination of personal data points such as name, ssn, phone number, address, and date of birth the api cross checks each input field against authoritative databases and returns detailed match indicators for each field, helping businesses assess the accuracy and legitimacy of a user's identity this robust, data driven verification process plays a critical role in compliance, fraud prevention, and secure onboarding key benefits multi attribute identity verification using trusted u s data sources field level match indicators (e g , name match, ssn match, dob match) reduces risk of synthetic identity fraud and impersonation improves user trust and onboarding speed common use cases banking & financial services (kyc/cip) verify consumer identities during account opening, credit applications, or lending decisions to meet regulatory compliance online marketplaces & gig economy platforms confirm legitimacy of users, sellers, drivers, or service providers before activation on the platform cryptocurrency & fintech platforms perform identity verification during wallet creation or crypto trading onboarding, reducing regulatory and fraud risk healthcare registration confirm patient identity using ssn and dob to avoid duplicate records and insurance fraud insurance onboarding & claims validate the identity of policyholders or claimants during online application or payout processes e commerce or bnpl (buy now pay later) platforms use full or partial ssn based verification to determine if users are legitimate before extending credit or high value services sample curl curl location 'https //api signzy us/api/v3/us kyc/eidv advance' \\ \ header 'content type application/json' \\ \ header 'authorization ' \\ \ data raw '{ "ssn" "", "dob" "", "addressline1" "", "city" "", "state" "", "zip" "", "firstname" "", "middlename" "", "lastname" "", "driverlicense" "", "email" "", "phone" "" }' curl location 'https //api preproduction signzy us/api/v3/us kyc/eidv advance' \\ \ header 'content type application/json' \\ \ header 'authorization ' \\ \ data raw '{ "ssn" "", "dob" "", "addressline1" "", "city" "", "state" "", "zip" "", "firstname" "", "middlename" "", "lastname" "", "driverlicense" "", "email" "", "phone" "" }' request body parameters parameter data type required description ssn string optional 9 digits or 4 digits, numeric only (no dashes) example 123456789 dob string optional date in yyyy mm dd format example 1990 09 21 addressline1 string optional house number, street name and unit number (i e 770 skokie blvd, unit 930) or po box (i e 1607 westminster dr) example 22 horizon cir note addresss line 2 is not required in input city string optional city name example aurora state string optional 2 letter uppercase u s state code example il zip string optional 5 digit u s zip code example 60501 firstname string optional given name example john middlename string optional middle initial or blank example a lastname string optional family name example doe driverlicense string optional driver’s license number example p620 7949 email string optional must be a valid email format example john doe\@gmail com phone string optional must be 10 digits, or prefixed with 1 or +1 followed by 10 digits digits only, no spaces or symbols example 9xxxxxxxxxx minimum input requirements provide one or more of the following ssn, phone, email, full address (addressline1, city, state, zip), or (firstname, lastname, dob) sample response { "result" { "score" 93 31, "scoredescriptions" \[ "address match", "full name match", "full dob match", "full phone match", "email no match", "na", "city exact match", "first 3 digits match", "state exact match" ], "addressmatchtype" "match", "namematchtype" "match", "dobmatchtype" "match", "phonematchtype" "match", "emailmatchtype" "no match", "ssnmatchtype" "na", "citymatchtype" "match", "zipmatchtype" "partial match", "statematchtype" "match", "driverlicensematchtype" "no dl available on record" }, "reason" "request successful", "code" "s001" } response body parameters parameter data type description score number (float) overall identity match score (0–100) scoredescriptions\[] array\[string] descriptions of individual field match results addressmatchtype string match status for address namematchtype string match status for name dobmatchtype string match status for date of birth phonematchtype string match status for phone number emailmatchtype string match status for email ssnmatchtype string match status for ssn citymatchtype string match status for city zipmatchtype string match status for zip code statematchtype string match status for state driverlicensematchtype string match status for driver’s license match types values logic description match type when data in input matches exactly with database match when data in input matches partially with database partial match when data in input does not match with database no match when no input is passed for corresponding data field na when no data is available in records (esp for dl) no dl available on record guidelines to use it is recommended to base decisions primarily on the score and match type values as a general guideline, a score above 70 indicates a strong match the score descriptions offer additional context on the matching logic used but are not intended for automated decision making purposes for automated decision making, we recommend use our score and elemental match/partial & no match you can use score description as part of your review process in case of borderline cases score descriptions values address logic description score descriptions full address match address match full address match on a previous/historical address prev address match full address match excluding the unit address match minus unit full address match on previous/historical address excluding the unit prev address match minus unit match on house number and first 4 chars of street name house number 1st four of street name match match on previous/historical house number and first 4 chars of street name prev house number 1st four of street name match house number match house number match house number match on previous/historical address prev house number match street name match street name match street name match on previous/historical address prev street name match no match on address address no match name field description score description full name match including middle if included in request full name match full name match (on aka) including middle if included in request prev full name match first and last names match, but not middle name first name last name match first and last names match on aka, but not middle name prev first name last name match last name and 1st 4 chars of first name match last name and 1st four of first name match last name and 1st 4 chars of first name of aka prev last name only match last name and 1st letter of first name match last name and 1st letter of first name match last name and 1st letter of first name match of aka prev last name only match last name only match last name only match last name only matches on aka prev last name only match first name only matches first name only match first name only matches on aka prev first name only match no name match name no match date of birth field description score description full dob match full dob match month and year match, not day month year match year of dob only match year match no dob match dob no match phone field description score description full phone match full phone match full phone match on previous/historical phone prev full phone match last 7 digits of phone match phone last 7 match last 7 digits of phone match or previous/historical phone prev phone last 7 match no phone match phone no match email field description score description full email match full email match user name only match username match no email match email no match no email available no email avail on record ssn field description score description ssn exact match ssn exact match last 4 digits of ssn match last 4 match last 4 digits of ssn when full ssn's are not permitted by access profile last 4 match redacted no ssn match ssn no match city field description score description city exact match city exact match city no match city no match zip field description score description zip code exact match zip exact match only 3 digits match of zip code match first 3 digits match zip no match zip no match state field description score description state exact match state exact match previous state match prev state exact match state no match state no match sample error e601 internal server error { "result" {}, "reason" "internal server error", "code" "e601" } e001 invalid regex { "result" {}, "reason" "bad request \\"ssn\\" must be 4 or 9 digits (numbers only)", "code" "e001" } \ { "result" {}, "reason" "bad request \\"dob\\" must be in yyyy mm dd", "code" "e001" } \ { "result" {}, "reason" "bad request in \\"dob\\" either month or date is invalid", "code" "e001" } \ { "result" {}, "reason" "bad request \\"dob\\" cannot be in future", "code" "e001" } \ { "result" {}, "reason" "bad request \\"dob\\" is invalid", "code" "e001" } \ { "result" {}, "reason" "bad request \\"phone\\" must be either 10 digits, 1 followed by 10 digits, or +1 followed by 10 digits ", "code" "e001" } \ { "result" {}, "reason" "bad request \\"state\\" length must be 2 characters long", "code" "e001" } \ { "result" {}, "reason" "bad request \\"zip\\" must be exactly 5 digits ", "code" "e001" } e001 empty required field { "result" {}, "reason" "minimum input not satisfied provide one or more of the following ssn, phone, email, full address (addressline1, city, state, zip), or (firstname, lastname, dob)", "code" "e002" } e401 upstream failure { "result" {}, "reason" "upstream error", "code" "e401" } error response parameters parameter description result empty result object reason reason for error status s tatus of the api c ode error code from signzy error codes http status code error code description 400 e001 bad request 401 e1001 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 success codes http status code success code description 200 s001 request successful 200 s003 data not found on source 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 help\@signzy com 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!