Wireless ID API Documentation
WirelessID API uses GET/POST methods and supports only HTTPS with TLS v1.2+. The service returns the accurate results of landline or wireless that can be relied upon for TCPA compliance.
We recommend limiting the API call rate to 10 per second. Check out the complete list of RealPhoneValidation API best practices here: realphonevalidation.com/api-best-practices/
Required Input Parameters:
| Parameter | Description |
|---|---|
| Output | (OPTIONAL) set to “json” or “xml”. Omitting this defaults to XML |
| Phone | 10 numeric digits ONLY |
| Token | Unique PW given by RealValidation |
Response Fields:
| Response Field | Description |
|---|---|
| ResponseCode | (See Appendix A below) |
| ResponseMsg | (See Appendix A below) |
Example: Wireless
https://api.realvalidation.com/rpvWebService/WirelessID.php?Phone=7275555555&token=1234ABCD-1234-ABCD-1234-123456ABCDEFResult in XML
<?xml version="1.0" encoding="UTF-8"?>
<response>
<RESPONSECODE>Landline</RESPONSECODE>
<RESPONSEMSG></RESPONSEMSG>
</response>Result in JSON
{
"RESPONSECODE":"Landline",
"RESPONSEMSG":{}
}Appendix A:
| Response Code | Response Message | Description |
|---|---|---|
| landline | Normal Hardline Phone | |
| cell | Mobile/Cellular Phone | |
| -1 | missing phone number | Phone number not submitted |
| -1 | bad-phone | Phone number is not valid in the USA |
| -1 | invalid format | Phone number must be 10 digits |
| -1 | unauthorized | Your token is not active |
| -1 | server-unavailable | Server cannot be contacted at the moment |
| HTTP 403 | Temporarily throttled due to exceeding the recommended 10/sec API calls |
Not super techie… integrate Wireless ID into your favorite CRM, forms, and apps using Zapier or Integrately.
