| Parameter Name | Description | Expected Values | Example |
| strictness | How in depth (strict) the reputation check should be. Stricter checks may provide a higher false-positive rate. We recommend starting at "0", the lowest strictness setting, and increasing to "1" or "2" depending on your levels of fraud. | Integer | strictness=1 |
| country | Optionally provide the default country or countries this phone number is suspected to be associated with. The API will prefer to use a country on this list for verification or will require a country to be specified in the event the phone number is less than 10 digits. | string or array of strings | country[]=UK |
| enhanced_line_check | Contact support to activate this feature. Enables more advanced active line checks through our HLR lookup service. This feature provides greater accuracy for identifying active or disconnected phone numbers including landline, mobile, and VOIP services. The "active_status" field is also populated when this feature is enabled. | bool | enhanced_line_check=true |
| sms_pumping | Enables detection of SMS pumping attacks, where perpetrators artificially inflate the volume of traffic sent to websites and app touchpoints protected by SMS authentication. | bool | sms_pumping=true |
| enhanced_name_check | Contact support to activate enhanced name appending for a phone number. Our standard phone validation service already includes extensive name appending data. | bool | enhanced_name_check=true |
Advanced Options
Additional Request Parameters
Custom Variables
You can pass custom tracking variables (such as userID and transactionID) established in your account settings with each API request. This allows our reporting tools to filter by specific variables such as users, products, campaigns, and transactions so you can easily match up records with your system to identify fraudulent activity.
Reporting Fraud and Improving Machine Learning
Train your account's machine learning algorithms to better identify fraud for your audience. You can use the following endpoint to report phone numbers as fraudulent. Please only report data that is highly likely to be abusive.
Replace USER_PHONE_HERE with the phone number to report.
Making Requests Without Passing API Key in URL
Due to the nature of platform requirements or frameworks, you may need to request the Phone Number Validation API endpoints without passing the API key to the URL. You can alternatively pass the Phone Validation API key via GET, POST, or Headers. These requests use the following endpoints:
JSON
XML
| Method | Value | Example |
| GET | key | key=YOUR_API_KEY&phone=18007132618 |
| POST | key | key=YOUR_API_KEY&phone=18007132618 |
| Header | IPQS-KEY (Additional parameters passed as either GET or POST) | IPQS-KEY: YOUR_API_KEY |
Bulk Phone Validation
You can upload a large list of phone numbers for batch processing through the Phone Number Validation API.
For information about bulk validation, see Bulk Validation CSV API.
Next Steps
Learn more about each of the variables included in the responses you receive.