Phone Insights Score

introduction the phone insights score api provides a comprehensive risk assessment of a user based solely on their phone number it aggregates data from carrier records, porting history, sim activity, and deactivation events to generate a trust score that reflects the reliability and authenticity of the user’s phone identity this api is a powerful tool for fraud prevention, risk profiling, and enhancing decision making during user onboarding or transaction verification a higher score indicates higher trustworthiness and lower risk associated with the phone number key benefits real time phone based risk scoring for fraud detection enhanced onboarding decisions using trusted telecom data reduced manual checks with automated risk signals seamless integration into kyc and fraud prevention workflows common use cases fintech & lending risk assessment evaluate risk of identity fraud before approving loans or credit using phone based risk indicators e commerce transaction verification use phone trust score to flag high risk users or transactions during checkout fraud prevention in digital wallets detect fraud or recently ported numbers before allowing sensitive actions like money transfers or password resets customer onboarding in telecom & utilities assess user legitimacy based on deactivation patterns and sim activity before issuing services authentication & login flows use score as an additional risk signal to trigger step up authentication or challenge mechanisms ride sharing, gig, or rental platforms quickly assess the trust level of new users or drivers/renters through phone number intelligence sample curl curl location 'https //api signzy us/api/v3/us kyc/phone insights score' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ "consentstatus" "", "phonenumber" "xxxxxxxxxx", "countrycode" "us", "consentoptintype" "whitelist", "consentoptinmethod" "tco", "consentoptinduration" "one", "consentoptinid" "xxxxxx", "consentoptintimestamp" "2019 09 18t00 13 37 667z", “consentoptinurl” “www example com” // optional field }' curl location 'https //api preproduction signzy us/api/v3/us kyc/phone insights score' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ "consentstatus" "optedin", "phonenumber" "xxxxxxxxxx", "countrycode" "us", "consentoptintype" "whitelist", "consentoptinmethod" "tco", "consentoptinduration" "one", "consentoptinid" "xxxxxx", "consentoptintimestamp" "2019 09 18t00 13 37 667z", “consentoptinurl” “www example com” // optional field }' request body parameters 100,127,152,100 true 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 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 sample response response { "result" { "requestid" "f4c0d35b 1a8e 437c a140 922121b2ce7c", "description" "success", "response" { "phonenumber" "xxxxxxxxx", "linetype" "wireless", "carrier" { "name" "xxx", "originalname" "xxxx xxx xxx", "ocn" "xxxx" }, "deactinfo" { "lastdeacttype" "", "lastdeactdate" "", "lastcarriername" "" }, "portinginfo" { "ported" "false", "tenure" { "mindays" "", "maxdays" "" }, "lastcarrier" { "name" "", "originalname" "" } }, "countrycode" "us", "score" 1000 } }, "reason" "request successful", "code" "s001" } response body parameters true 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 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 sample error e601 internal server error { "result" {}, "reason" "internal server error", "status" "failure", "code" "e601" } e001 invalid regex { "result" {}, "status" "failure", "reason" "bad request \\"consentstatus\\" must be one of \[optedin, optedout, notcollected, unknown]", "code" "e001" } \ { "result" {}, "reason" "bad request \\"phonenumber\\" must start with +1 or 1 and be followed by exactly 10 digits ", "code" "e001" } \ { "result" {}, "status" "failure", "reason" "bad request \\"countrycode\\" must be one of \[us, ca]", "code" "e001" } \ { "result" {}, "reason" "bad request \\"consentoptintype\\" is not valid ", "code" "e001" } e001 empty required field { "result" {}, "status" "failure", "reason" "bad request \\"phonenumber\\" is not allowed to be empty", "code" "e001" } e401 upstream failure { "result" {}, "reason" "upstream error", "status" "failure", "code" "e401" } e001 invalid phone number // regex passed but phone number is invalid { "result" {}, "reason" "bad request \\"phonenumber\\" entered is invalid", "code" "e001" } 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 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 success codes true 203,203,203 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type 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!