Identity Fill (v2)

introduction the identity fill (v2) api (us) enables the retrieval of verified customer information using minimal input—such as a phone number, dob, or ssn etc it is designed to streamline digital onboarding processes by auto filling application forms with accurate personal data, thereby reducing friction, minimizing manual errors, and significantly enhancing the overall user experience this api is especially useful in scenarios where rapid, secure identity verification is needed with minimal effort from the end user key benefits faster form completion with minimal input improved conversion rates by reducing drop offs during onboarding accurate data prefill, minimizing typos or misinformation reduced fraud risk by verifying identity from trusted sources common use cases digital onboarding for financial services prefill bank account opening, credit card, or loan applications using just phone number and ssn accelerate kyc (know your customer) checks for regulatory compliance e commerce & checkout optimization autofill shipping and billing information to reduce cart abandonment insurance application prefill populate insured's personal data (name, dob, address) to reduce form fatigue and improve submission rates telecom or utility service enrollment streamline sign up for phone, internet, or energy services using limited user input identity verification for gig or rental platforms prefill background check and id verification forms for faster user onboarding healthcare patient registration populate intake forms securely with verified identity data using ssn & phone, reducing administrative overhead sample curl curl location 'https //api signzy us/api/v3/us/identity fill v2' \\ \ header 'content type application/json' \\ \ header 'authorization ' \\ \ data raw '{ "ssn" "", "dob" "", "addressline1" "", "addressline2" "", "city" "", "state" "", "zip" "", "firstname" "", "middlename" "", "lastname" "", "driverlicense" "", "email" "", "phone" "" }'curl location 'https //api preproduction signzy us/api/v3/us/identity fill v2' \\ \ header 'content type application/json' \\ \ header 'authorization ' \\ \ data raw '{ "ssn" "", "dob" "", "addressline1" "", "addressline2" "", "city" "", "state" "", "zip" "", "firstname" "", "middlename" "", "lastname" "", "driverlicense" "", "email" "", "phone" "" }' minimum input requirements provide one or more of the following (phone ,dob), (phone , ssn), (firstname , ssn), (firstname , lastname, ssn), (firstname, lastname, phone), or (firstname, lastname, dob) request body parameters true 165,165,164,167left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type sample response { "result" { "matches" \[ { "score" "100 00", "isresidential" "false", "isresidentialmessage" "", "addresshighriskflag" "", "addresshash" "", "firstname" { "value" "john", "matchtypecode" "match" }, "middlename" { "value" "a", "matchtypecode" "na" }, "lastname" { "value" "doe", "matchtypecode" "match" }, "name" { "prefix" "", "firstname" "john", "middlename" "a", "lastname" "doe", "suffix" "", "rawnames" \[ "john a doe" ], "publicfirstseendate" "2020 01 01", "totalfirstseendate" "2016 01 01", "sourcesummary" "" }, "ssn" { "value" "123 45 6789", "matchtypecode" "match" }, "socialsecuritynumbers" \[ { "ssn" "123 45 6789", "dates" "", "location" "", "alternatelocation" "", "sourcesummary" "" } ], "dobmonth" { "value" "12", "matchtypecode" "match" }, "dobday" { "value" "10", "matchtypecode" "match" }, "dobyear" { "value" "1985", "matchtypecode" "match" }, "age" { "value" "39", "matchtypecode" "na" }, "driverlicense" { "value" "xxxxxxx", "matchtypecode" "na" }, "addresses" \[ { "value" "123 main st; sample city, ca 90001", "matchtypecode" "na" }, { "value" "45 oak avenue, unit 4; sample city, ca 90002", "matchtypecode" "na" } ], "cities" \[ { "value" "sample city", "matchtypecode" "na" } ], "states" \[ { "value" "ca", "matchtypecode" "na" } ], "zips" \[ { "value" "90001", "matchtypecode" "na" } ], "addresshistory" \[ { "isdeliverable" "true", "ismergedaddress" "false", "ispublic" "true", "addressqualitycodes" \[], "addresshash" "1234567890123456789", "housenumber" "123", "streetpredirection" "", "streetname" "main", "streetpostdirection" "", "streettype" "st", "unit" "", "unittype" "", "city" "sample city", "state" "ca", "county" "sample county", "zip" "90001", "zip4" "0001", "dpc" "01", "latitude" "34 000000", "longitude" " 118 000000", "addressorder" "1", "highriskmarker" { "ishighrisk" "false", "sic" "", "addresstype" "" }, "propertyindicator" "", "bldgcode" "", "utilitycode" "", "unitcount" " 1", "firstreporteddate" "2020 01 01", "lastreporteddate" "2025 01 01", "publicfirstseendate" "2021 01 01", "totalfirstseendate" "2021 01 01", "phonenumbers" \[], "neighbors" \[], "neighborsummaryrecords" \[], "fulladdress" "123 main st; sample city, ca 90001", "sourcesummary" "" } ], "phonehistory" \[ { "phonenumber" "(555) 123 4567", "company" "sample telecom", "location" "samplecityca", "phonetype" "wireless", "isconnected" "true", "ispublic" "true", "latitude" "34 000000", "longitude" " 118 000000", "phoneorder" "1", "firstreporteddate" "2019 01 01", "lastreporteddate" "2025 01 01", "publicfirstseendate" "2020 01 01", "totalfirstseendate" "2019 01 01", "sourcesummary" "" } ], "emailhistory" \[ { "emailaddress" "john doe\@example com", "emailordinal" "1", "ispremium" "true", "nonbusiness" "1", "sourcesummary" "" } ], "emails" \[ { "value" "john doe\@example com", "matchtypecode" "na" } ], "phones" \[ { "value" "(555) 123 4567", "matchtypecode" "match" } ], "akas" \[ { "firstname" { "value" "jon", "matchtypecode" "na" }, "middlename" { "value" "", "matchtypecode" "na" }, "lastname" { "value" "doe", "matchtypecode" "na" } } ], "datesofbirth" \[ { "dob" "1985 12 10", "age" "39", "sourcesummary" "" } ], "datesofdeath" \[], "deathrecords" { "isdeceased" "false", "sourcesummary" "" }, "indicators" "", "iscurrentpropertyowner" "not available", "driverlicensedetails" \[], "ispublic" "true", "isoptedout" "false", "optoutdate" "1970 01 01" } ], "requestid" "1234567890abcdef" }, "reason" "request successful", "code" "s001" } response body parameters inside each matches object true 220,220,221left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type address true 220,220,221left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type phone true 220,220,221left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type email true 220,220,221left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type additional fields true 220,220,221left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type sample error e601 internal server error { "result" {}, "reason" "internal server error", "status" "failure", "code" "e601" } e001 invalid regex { "result" {}, "reason" "bad request \\"ssn\\" must be 9 digits (numbers only)", "code" "e001" } \ { "result" {}, "reason" "bad request \\"dob\\" must be in yyyy mm dd", "code" "e001" } \ { "result" {}, "reason" "bad request \\"phone\\" must be of 10 digits", "code" "e001" } \ { "result" {}, "reason" "bad request \\"email\\" must be a valid email", "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" "bad request invalid input combination required combinations (phone + dob), (phone + ssn), (firstname + ssn), (firstname + lastname + ssn), (firstname + lastname + phone), or (firstname + lastname + dob) ", "code" "e001" } e401 upstream failure { "result" {}, "reason" "upstream error", "status" "failure", "code" "e401" } e001 bad request { "result" {}, "status" "failure", "reason" "bad request", "code" "e001" } e301 data not found { "result" {}, "reason" "data not found", "code" "e301" } error response parameters true 304,305left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type error codes true 4 203,203,203 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type success codes true 220,220,221left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type 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 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!