Turbo v3 API Documentation

The RealPhoneValidation Turbo API uses GET/POST methods and supports only HTTPS with TLS v1.2+. Determines connectivity in a flash, and you get the industry’s best in connect/disconnect information in about 2 seconds.

Required Input Parameters:

Output(OPTIONAL) set to “json” or “xml”. Omitting this defaults to XML
Phone10 numeric digits ONLY
TokenUnique PW given by RealValidation

Response Fields:

Response FieldDescription
Status(See Appendix A below)
Error_Text(See Appendix A below)
Phone_TypeMobile, Landline, or VoIP
Caller_Name (subscriber name)Name of person associated with phone (if available)
CarrierService provider. Such as Verizon, AT&T, etc.
Caller_Type (subscriber type)Consumer, Business, or Unavailable

Example: Connected Phone Line


Result in XML

<?xml version="1.0" encoding="UTF-8"?>
   <caller_name>Jack Smith</caller_name>
   <carrier>Verizon Wireless:6006 - SVR/2</carrier>

Result in JSON

"caller_name":"Jack Smith",
"carrier":"Verizon Wireless:6006 - SVR\/2"

Appendix A:

StatusError TextDescription
connectedTypically connected
connected-75Connected 75% of the time
pendingNot completed yet
disconnectedTypically disconnected
disconnected-70Disconnected 70% of the time
unreachableNot reachable
invalid phonePhone not valid
restrictedCan’t be dialed
ERRORbad phone number
ERRORmissing token
unauthorizedtoken is not valid
invalid-formatphone or zip are not in a valid format
invalid-phonephone number is not valid
bad-zip-codezip code is not valid
server-unavailablevarious messagesContact support

Not super techie… integrate Turbo v3 into your favorite CRM, forms, and apps using Zapier or Integrately.

Turbo v3 API Doc
Turbo v3 API 060222

Before you go...

Are you currently using a
phone validation service?

Scroll to Top