Reassigned Number Lookup API Documentation

The Reassigned Number Lookup API uses GET/POST methods and supports only HTTPS with TLS v1.2+. Determines if a phone number has been reassigned (changed ownership) since your last date of consent.
Required Input Parameters:
Parameter
Description
output
(OPTIONAL) set to “json” or “xml”. Omitting this defaults to XML
phone
10 numeric digits ONLY
contact_date
In YYYY-MM-DD format. The date you received permission to contact.
Token
Unique PW given by RealValidation
Response Fields:
Response Field
Description
RESPONSECODE
-1 for a problem. OK if successfully submitted
RESPONSEMSG
Human readable message for errors. Text varies. Blank on success.
reassigned
Determines if the number has been reassigned since the date you have provided (See Appendix A)
id
An alphanumeric internal identifier for your lookup
Example: Connected Phone Line
https://api.realvalidation.com/rpvWebService/ReassignedNumberLookup.php?phone=7275555555&contact_date=2010-01-01&token=1234ABCD-1234-ABCD-1234-123456ABCDEF
Result in XML
<?xml version="1.0" encoding="UTF-8"?>
<response>
<RESPONSECODE>OK</RESPONSECODE>
<RESPONSEMSG/>
<reassigned>no_data</reassigned>
<id>13</id>
</response>
Result in JSON
{
	"RESPONSECODE":"OK",
	"RESPONSEMSG":"",
	"reassigned":"yes",
	"id":"4-C"
}
Appendix A:
Status
Error Text
Description
yes

The number was reassigned after date provided
no

The number has not been reported as reassigned after date provided
no data

No changes were recorded by phone carriers since the required date of January 27th, 2021
undetermined

Check formatting to make sure it adheres to the documentation. Then contact us.

Not super techie... integrate RealPhoneValidation services into your favorite CRM, forms, and apps using Zapier or Integrately.

RPV Turbo Standard API Doc
Right Party Number Verification 03062023