Phone ID Intelligence
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.
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.
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% |
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
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 |

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. |

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.
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.
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 [email protected]. 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!