> ## Documentation Index
> Fetch the complete documentation index at: https://docs.greip.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Phone Number Scoring
> This method serves as an additional layer of protection in your system for validating phone numbers. It not only checks the syntax but also assesses the likelihood of the phone number being valid and operational.
By incorporating this scoring into your workflow, you can enhance fraud detection, reduce invalid inputs, and improve the overall quality of data captured.
export const MCPCallout = () => {
return
;
};
### Query Parameters
The phone command is used to specify the phone number you want to validate.
Expected values: a phone number
Sample value: `+12121234567`, `0012121234567`, `12121234567`, or `2121234567`
The `ISO 3166-1 alpha-2` format of the country code of the phone number. [Learn more](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)
Sample value: `US`
The format command is used to get a response in a specific format.
Expected values: `JSON`, `XML`, `CSV`, or `Newline`
For more information please refer to [Response Format](/options/response-format).
The mode command is used to in the development stage to simulate the integration process before releasing it to the production environment.
Expected values: `live`, or `test`.
For more information please refer to [Development Environment](/options/development-environment).
The userID command can be used to identify requests sent by specific users to monitor in the [Events Page](/dashboard-guides/monitoring-capabilities/real-time-threat-monitoring).
Expected values: email address, phone number, user id, name, etc.
For more information please refer to [User Identifier](/options/user-identifier).
The callback command can help you make the response as a JSONP format.
Expected values: any name that can be used as a function name in Javascript, e.g: `myFunctionName`.
For more information please refer to [JSONP Callback](/options/jsonp-callback).
```json Success theme={null}
{
"data": {
"carrier": "",
"reason": "Invalid phone number structure.",
"isValid": false,
"blacklisted": false,
"disposable": false,
"phone": "+12121234567",
"countryCode": "US",
"custom_rules_applied": {
"total": 0,
"rules": []
}
},
"status": "success",
"executionTime": 1
}
```
```json Error theme={null}
{
"status": "error",
"code": 101,
"type": "invalid_key",
"description": "The API Key is missing or invalid."
}
```
### Response properties
Carrier name of the phone number.
The reason behind considering this phone number as risky.
**Note:** The value of this property will be empty if the `isValid` is `true`.
A boolean value that you can rely on to determine if the phone number is 100% safe & valid or not.
Indicates if the phone number is blacklisted due to applying [custom
rules](/knowledge-base/custom-rules/overview) or were found in one of your
blacklists.
A boolean value that indicates if the phone number is a disposable phone number or not.
The phone number you sent in the request.
The country code you sent in the request.
The custom rules applied to this request, [learn
more](/knowledge-base/custom-rules/overview).
The total number of custom rules applied to this request.
The custom rules applied to this request, [learn
more](/knowledge-base/custom-rules/overview).
The rule ID as shown in the dashboard (e.g: `CR104`).
The rule title you set when creating the rule.
The response status.
Expected values: `success`, or `error`.
Time spent in milliseconds to process the data.
## What can I expect from this API?
* Detection of disposable phone numbers (also known as Temporary Phone Numbers) or numbers associated with VoIP services
* Validation of phone number syntax