Phone ID Intelligence

overview and purpose the phone number intelligence api offers an advanced solution for assessing the risk profile of phone numbers by submitting a phone number, businesses can receive a comprehensive analysis of each identifier's risk level this service evaluates the provided information and generates a risk score, indicating the potential risk associated with the current transaction this api is designed to empower organizations with vital insights into transactional risks it not only provides a numeric risk score but also delivers a set of detailed insights and reason codes these elements offer granular and contextual intelligence, shedding light on the digital behavior that influences the risk score the primary goal of the phone number intelligence api is to enable businesses to make more informed decisions regarding transaction security by understanding the risk profiles of phone numbers, ip addresses, and email addresses, companies can effectively prevent fraudulent activities, verify user identities, and enhance the overall trustworthiness and security of their transactions use cases the phone number intelligence api serves a wide range of applications, each focused on enhancing security, managing risk, and fostering trust in different scenarios its versatility is evident in various sectors and operations fraud prevention it plays a crucial role in detecting and preventing fraudulent activities like account takeovers, identity theft, or fake account creation by analyzing the risk associated with phone numbers during registration or transactions identity verification the api assists in verifying the authenticity of a user's phone number, aligning it with the provided identity to diminish identity fraud risks transaction risk assessment in financial contexts, it evaluates the risk level of phone numbers involved in transactions, such as money transfers, helping to pinpoint potentially dubious activities user onboarding during new user registration processes, the api assesses the risk of the provided phone number, aiding in decision making for account creation approval or further scrutiny authentication and authorization it enhances security protocols by integrating phone number risk assessment into multi factor authentication systems, thereby preventing unauthorized access compliance and regulatory adherence the api is crucial in ensuring compliance with regulations, especially in industries with stringent requirements, by authenticating phone numbers and identifying associated risks account management for ongoing account maintenance, it continuously monitors phone numbers for risk, enabling proactive detection and response to suspicious activities telecommunications and mobile services telecommunication companies utilize this api to evaluate the risk associated with new phone number activations, aiming to detect and prevent misuse or fraud e commerce the api aids in preventing fraudulent transactions, account takeovers, and fake reviews by assessing the risk of phone numbers used in online purchases and reviews marketplace and classifieds it enhances the reliability of transactions in marketplaces and classifieds by verifying phone numbers of sellers and buyers, thereby reducing the chances of fraudulent listings and transactions countries supported below are the list of countries supporoted and the coverage they support country coverage afghanistan <30% albania 30 50% algeria <30% andorra 30 50% angola 30 50% argentina <30% armenia <30% australia 30 50% austria 30 50% azerbaijan <30% bahrain 30 50% bangladesh <30% belarus <30% belgium 60 80% belize 30 50% bhutan <30% bolivia 30 50% bosnia and herzegovina <30% botswana <30% brazil 95% bulgaria 30 50% burkina faso <30% burundi <30% cambodia <30% cameroon <30% canada 60 80% cape verde 30 50% chad <30% chile 30 50% china <30% colombia 30 50% congo <30% costa rica 50 60% croatia 30 50% cuba <30% cyprus 80% czech republic 30 50% denmark 50 60% djibouti <30% ecuador 30 50% egypt 30 50% el salvador <30% equatorial guinea <30% eritrea <30% estonia 30 50% ethiopia <30% faroe islands <30% fiji <30% finland 30 50% france 30 50% french polynesia 30 50% gabon 30 50% georgia 50 60% germany 30 50% ghana <30% gibraltar 30 50% greece 30 50% guatemala <30% guinea <30% guyana 30 50% haiti <30% honduras 30 50% hong kong <30% hungary 30 50% iceland 30 50% india 30 50% indonesia <30% iran 30 50% iraq 30 50% ireland 30 50% israel 30 50% italy 60 80% japan 30 50% jordan <30% kazakhstan <30% kenya <30% kiribati <30% kuwait 30 50% kyrgyzstan <30% laos <30% latvia 30 50% lebanon 40 60% lesotho <30% liberia <30% libya 30 50% liechtenstein 30 50% lithuania 30 50% luxembourg 50 60% madagascar <30% malawi <30% malaysia 30 50% maldives 30 50% mali <30% malta 80% mauritania <30% mauritius <30% mexico 30 50% micronesia <30% moldova <30% monaco <30% mongolia <30% montenegro <30% morocco 30 50% namibia 30 50% nepal <30% netherlands 30 50% new zealand 30 50% nicaragua <30% niger <30% nigeria <30% north korea <30% norway 80% oman 30 50% pakistan <30% palestine 30 50% panama <30% papua new guinea <30% paraguay 30 50% peru 30 50% philippines <30% poland 30 50% portugal 80% qatar 30 50% romania 30 50% russia <30% rwanda <30% san marino <30% saudi arabia 30 50% senegal <30% serbia 30 50% seychelles 30 50% sierra leone <30% singapore 30 50% slovakia 30 50% slovenia 30 50% solomon islands <30% south africa <30% south korea <30% spain 30 50% sri lanka <30% sudan <30% suriname <30% swaziland <30% sweden 50 60% switzerland 30 50% syria 30 50% taiwan 30 50% tajikistan <30% tanzania <30% thailand 30 50% tonga <30% tunisia 30 50% turkey 30 50% turkmenistan <30% uganda <30% ukraine <30% united arab emirates 30 50% united kingdom 50 60% united states 85 99% uruguay <30% uzbekistan <30% vanuatu <30% venezuela 30 50% vietnam <30% yemen <30% api details the api request will need an authorization token in the header the only input it needs is the phonenumber the phonenumber should also include country code sample curl curl location 'https //api preproduction signzy us/api/v3/global/risk score' \\ \ header 'authorization \<auth token>' \\ \ header 'content type application/json' \\ \ data '{ "phonenumber" "916301418535" }'curl location 'https //api signzy us/api/v3/global/risk score' \\ \ header 'authorization \<auth token>' \\ \ header 'content type application/json' \\ \ data '{ "phonenumber" "916301418535" }' request body parameters parameter data type description phonenumber string enter the phone on which you want to perform the check note that the country code is important(remove any special characters like "+" or " " while entering the number detailed response { "result" { "completephonenumber" "16022810271", "countrycode" "1", "phonenumber" "6022810271", "riskinsights" { "category" \[ { "categorycode" "10010", "categoryname" "low activity ", "categorymeaning" "not enough activity or attributes to classify the transaction as either risky or trustworthy " } ], "applicationtopersonmessaging" \[ { "code" "22005", "codename" "seen in the last 15 days ", "codemeaning" "this number was seen in verification traffic in the last 15 days " }, { "code" "20011", "codename" "low long term activity ", "codemeaning" "low volume of verification traffic on this phone number over the past 90 days " }, { "code" "20013", "codename" "no range activity ", "codemeaning" "very little activity, or none at all, for a risky range that this number belongs to over the past 90 days also returned if the number does not belong to a risky range " } ], "numbertype" \[] }, "location" { "city" "", "state" "", "zip" "", "metrocode" "", "county" "", "country" { "name" "united states", "iso2" "us", "iso3" "usa" } }, "carrier" { "name" "at\&t wireless" }, "blocklisting" { "blocked" "", "blockcode" "", "blockdescription" "not blocked" }, "risk" { "level" "low", "recommendation" "allow", "score" 1 } } } response body parameters parameter data type description completephonenumber string the full phone number including the country code as submitted in the request countrycode string the country code extracted from the complete phone number phonenumber string the local part of the phone number, excluding the country code riskinsights object a collection of detailed insights into various risk categories associated with the phone number riskinsights category array information on the general risk category of the phone number, including code, name, and meaning riskinsights applicationtopersonmessaging array insights related to the phone number's activity in verification traffic, with details like code, code name, and code meaning riskinsights numbertype array additional details regarding the type of phone number, if available location object geographical location information associated with the phone number, including city, state, and country details location city string the city associated with the phone number location state string the state associated with the phone number location zip string the zip code associated with the phone number location metrocode string the metro code associated with the phone number, if available location county string the county associated with the phone number location country object country details including name and iso codes carrier object information about the telecommunication service provider of the phone number carrier name string the name of the telecommunication service provider blocklisting object information regarding the blocklisting status of the phone number blocklisting blocked string indicates if the phone number is blocked blocklisting blockcode string the code associated with the blocklisting status blocklisting blockdescription string description of the blocklisting status risk object summarized risk assessment for the phone number risk level string the overall risk level associated with the phone number (e g , low, medium, high) risk recommendation string the recommended action based on the risk score (e g , allow, review, block) risk score integer the numerical risk score assigned to the phone number reason codes the api returns specific reason codes that help in understanding the risk profile associated with a phone number these codes are categorized and each has a unique name and meaning category the reason codes are grouped under different categories each category reflects a certain aspect of the phone number's risk or behavior profile code every reason code is identified by a unique numerical value (e g , 10010 , 10020 ) this code is a key identifier used in the api response name each code has a corresponding name, which provides a brief label or title for the code (e g , "low activity", "low regular activity") meaning the meaning of each code offers a detailed explanation of what the code represents this description helps in understanding the specific aspect of the phone number's behavior or risk profile that the code is referring to (e g , "not enough activity or attributes to classify the transaction as either risky or trustworthy", "trustworthy category, based on past behavior") this mapping is crucial for interpreting the risk insights provided by the api, enabling businesses to make informed decisions based on the nuanced analysis of phone numbers used in transactions scoring logic range risk level action description 0 100 low allow transaction with insufficient risk indicators 101 200 medium low allow transaction with significant confidence building behavior on network 201 300 high allow suspicious transaction 301 470 high allow suspicious transaction 471 920 very high block risky transaction 921 1000 very high block risky transaction this table represents the risk scoring system used by the api, where a high score indicates a higher risk the 'recommendation' column suggests actions such as 'allow', 'flag', or 'block' based on the risk level, while the 'comments' column provides additional context for each score range sample error 400 bad request { "error" { "name" "error", "message" "phonenumber is required", "reason" "validation error", "type" "bad request", "statuscode" "400" } } 401 unauthorized { "message" "no api key found in request" } 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!