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 parameter data type required description ssn string optional must be exactly 9 digits (numeric only) example 123456789 dob string optional must be in yyyy mm dd format validated to be a real date , not future , and not older than 200 years example 1990 01 01 addressline1 string optional house number, street name, or po box example 123 main street addressline2 string optional additional address information (apartment, unit, suite) city string optional city name example samplecity state string optional must be 2 uppercase alphabets example ca zip string optional must be exactly 5 digits example 90001 firstname string optional given name example john middlename string optional middle initial or blank example m lastname string optional family name example doe driverlicense string optional driver’s license number (state specific format allowed) example d1234567 email string optional must be a valid email format example john doe\@example com phone string optional must be exactly 10 digits (numeric only) example 1234567890 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 parameter data type description score string match confidence score in percentage firstname string first name associated with the matched identity middlename string middle name or middle initial of the matched identity lastname string last name / family name of the matched identity name object full name object containing prefix, suffix, and raw name variations ssn string masked social security number associated with the identity dob string date of birth in yyyy mm dd format (derived from year, month, and day in the response ) age string age derived from the date of birth driverlicense string masked driver’s license number, if available address parameter data type description addresses array of objects list of known address strings associated with the individual addresshistory array of objects structured address records including deliverability, geolocation, reporting dates, and formatted address cities array of objects list of cities associated with the matched identity states array of objects list of u s states associated with the identity zips array of objects list of zip codes associated with the identity isresidential string indicates whether the address is a residential address addresshighriskflag string indicates whether the address is marked as high risk phone parameter data type description phones array of objects phone numbers associated with the identity (values masked or generic) phonehistory array of objects historical phone metadata such as carrier, type, reporting dates, and connectivity status email parameter data type description emails array of objects email addresses associated with the identity emailhistory array of objects historical email metadata such as first seen dates and source information additional fields parameter data type description akas array of objects known aliases or alternative name variations for the individual datesofbirth array list of birthdates found from different sources datesofdeath array death record details, if available (empty if the person is alive) deathrecords object indicates whether the individual is deceased indicators string additional verification or risk indicators ispublic string indicates if the data is publicly available isoptedout string indicates whether the individual has opted out of data reporting optoutdate string date associated with the opt out request iscurrentpropertyowner string indicates property ownership status, if available 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 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 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!