NAV Navbar
Browser PHP PYTHON

Data247 Version 3 API Introduction

Welcome to the Data247 API! You can use our API to access various data services we provide.

We have example code in Browser , PHP, PYTHON, and JAVASCRIPT! You can view code examples in the dark area to the right, and you can switch the programming language of the examples with the tabs in the top right.

Base url for our api for version 3 is https://api.data247.com/v3.0

If you have any further questions. Feel free to contact us.

Authentication

Data247 requires an API key to allow access to the API. If you haven't signed-up for an account yet, you can sign up here . Then to get an API key, go to the "Account" menu, and select "API Key/Password"

Data247 expects the API key to be included in all API requests to the server as a query parameter key=my_api_key:

General API Format

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=B
    
    
    GET/POST Request 
    <?php 
        // Replace key value with your own api key
        $url = "https://api.data247.com/v3.0?key={my_api_key}&api=B";
        $result = @file_get_contents($url);
        if ($result){
            $result = @json_decode($result, true);
            if (!empty($result['response']['status']) && $result['response']['status'] == 'OK'){
                echo 'Balance: '.$result['response']['results'][0]['balance'];
            }
        }

    ?>
    
    GET/POST Request 
    import requests

    try:
        r = requests.get('https://api.data247.com/v3.0?key={my_api_key}&api=B')
        adict = r.json()['response']
        if 'status' in adict and adict['status'] == 'OK':
            print("Balance: {}".format(adict['results'][0]['balance']))
    except Exception as err:
        print('Error: '+ str(err))
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "balance": "123"
                 }
             ]
         }
    }
    

Data247 provides many different data services. Each data service is represented by a unique letter code/codes. You must provide the letter code which corresponds to the data service you wish to use. Data247 data service codes can be provided as a value of the query parameter api. For example: api=MT. Please see each data service section to find the correct letter code and the required fields for each service.

In addition the to data service code you must provide an api key which is used for authentication. See the "Authentication" section above.

By default the api results are returned in JSON format. If you want the result in another format you can explicitly specify it as a value of query parameter out. For example: out=xml or out=csv.

Data247 supports both GET or POST requests, So api request url can take a form of:
https://api.data247.com/v3.0?key={my_api_key}&api=MT&phone={phone}
Here {my_api_key} is your api key, MT in api=MT is the data service code for the Text@ data service and {phone} is the field required by the Text@ data service.

Parameter Required? Default Description
key required Your api key used for authentication
api required Unique Data247 data service letter code, Please refer to each data service section for appropriate code to be used
out optional json Api result format, Possible values json, xml, csv.
addfields optional Comma separated additional fields besides default fields you want it to be returned.
fields optional Comma separated fields you want it to be returned. It will only return these fields.
For other required fields to be used depending on data service api please refer to respective data service section.

API Response Format

The API response is always wrapped inside a response tag in the case of xml or response key for JSON.
Inside the response key or tag, there will always be a status key; this key describes the outcome the API request. If the API request is successful and returns data, then the status key value will be set to OK and all api data will be wrapped inside results key or tag.
In the case of a query failure, the value of the status key will be one of the error codes listed below.

EXAMPLES
Successuful JSON Response

{ "response": { "status": "OK", "results": [ { "balance": 86.9348 } ] } }



Successful XML response

<response> <status>OK</status> <results> <result> <api>B</api> <status>OK</status> <balance>86.934800</balance> </result> </results> </response>

Error JSON REsponse

{ "response": { "status": "D247_INVALID_API_KEY", "message": "Incorrect api key" } }

Error XML Response

<response> <status>D247_INVALID_API_KEY</status> <message>Incorrect api key</message> </response>

MESSAGING SERVICES [M]

Text@

Data Service Code: MT

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=MT&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=MT&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=MT&phone={phone_number}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "phone": "1234..",
                    "wless": "y",
                    "carrier_name": "Turkcell (Turk Telekom)",
                    "carrier_id": "9087",
                    "sms_address": "smsgateway@example.com",
                    "mms_address": "mmsgateway@example.com"
                 }
             ]
         }
    }
    

Text@ retrieves the Carrier name, iswireless, email-to-SMS, and email-to-MMS gateway addresses for your wireless phone numbers.
For now you can only provide US/Canada phone numbers.

Example HTTP Request URL:

For Single Phone
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=MT&phone={phone_number}

For Multiple Phones at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=MT

JSON BODY { "MT": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"} ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=MT&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Text@ data service. It's value is alphabet MT
phone required Phone number you want to look up Text@ information of.
For now it only accepts US/Canada number.
out optional json Api result format, Possible values json, xml, csv.
fields optional Comma separated fields you want it to be returned. It will only return these fields. See response section for fields to be used.
addfields optional Comma separated additional fields besides default fields you want it to be returned. For this api you can request these fields: billable, cost, git, region, ocn, indata, mcc, mnc
If you want to lookup Text@ information of multiple phone numbers(upto 20) at once then there are two alternatives:

1) Multiple phones can be provided as json body of request data as {"MT":[{'phone': "phoneNumber1"}, {"phone": "phoneNumber2"}]} where 'C' is data service code and phoneNumber1, phoneNumber2 are actual phone numbers you want to lookup carrier information of

2) Instead of phone as query parameter you can provide p1={phone1}&p2={phone2} &...p20={phone20} up to 20 phone numbers as get parameter.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
carrier_name: carrier name of provided number
carrier_id:: Carrier id of carrier
sms_address: SMS gateway address of number
mms_address: MMS gateway address of number
wless: whether number is wireless or not, Possible values: y or n
phone:Provided phone

CARRIER INFORMATION SERVICES [C]

Carrier247 (USA)

Data Service Code: CU

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=CU&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=CU&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=CU&phone={phone_number}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "phone": "1234..",
                    "wless": "y",
                    "carrier_name": "Turkcell (Turk Telekom)",
                    "carrier_id": "9087",
                    "sms_address": "smsgateway@example.com",
                    "mms_address": "mmsgateway@example.com"
                 }
             ]
         }
    }
    

Carrier247 (USA) returns Carrier name, iswireless, email-to-SMS, and email-to-MMS gateway addresses for provided domestic US phone numbers.

Example HTTP Request URL:

For Single Phone
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=CU&phone={phone_number}

For Multiple Phones at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=CU

JSON BODY { "CU": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"} ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=CU&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Carrier247 (USA) data service. It's value is CU
phone required Phone number you want to look up carrier information of.
out optional json Api result format, Possible values json, xml, csv.
If you want to lookup carrier information of multiple phone numbers(upto 20) at once then there are two alternatives:

1) Multiple phones can be provided as json body of request data as {"CU":[{'phone': "phoneNumber1"}, {"phone": "phoneNumber2"}]} where 'CU' is data service code and phoneNumber1, phoneNumber2 are actual phone numbers you want to lookup carrier information of

2) Instead of phone as query parameter you can provide p1={phone1}&p2={phone2} &...p20={phone20} up to 20 phone numbers as get parameter.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
carrier_name: carrier name of provided number
carrier_id:: Carrier id of carrier
sms_address: SMS gateway address of number
mms_address: MMS gateway address of number
wless: whether number is wireless or not, possible value y or n
phone: Provided phone

Carrier247 (International)

Data Service Code: CI

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=CI&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=CI&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=CI&phone={phone_number}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "phone": "1234..",
                    "wless": "y",
                    "carrier_name": "Turkcell (Turk Telekom)",
                    "carrier_id": "9087",
                    "country": "Turkey",
                    "isoCountry2": "TR"
                 }
             ]
         }
    }
    

Carrier247 (International)returns carrier information for international phone numbers, including whether they are wireless or landline numbers.
You must provide country code in your phone number.

Example HTTP Request URL:

For Single Phone
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=CI&phone={phone_number}

For Multiple Phones at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=CI

JSON BODY { "CI": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"}, ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=CI&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Carrier247 (International) data service. It's value is CI
phone required Phone number you want to look up carrier information of.
Please note that you must provide phone with country code
out optional json Api result format, Possible values json, xml, csv.
If you want to lookup carrier information of multiple phone numbers(upto 20) at once then there are two alternatives:

1) Multiple phones can be provided as json body of request data as {"CI":[{'phone': "phoneNumber1"}, {"phone": "phoneNumber2"}]} where 'C' is data service code and phoneNumber1, phoneNumber2 are actual phone numbers you want to lookup carrier information of

2) Instead of phone as query parameter you can provide p1={phone1}&p2={phone2} &...p20={phone20} up to 20 phone numbers as get parameter.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
carrier_name: carrier name of provided number
carrier_id:: Carrier id of carrier
phone: Provided phone
wless: whether number is wireless or not
country:: Country number belongs to
isoCountry2:: Two letter iso country code of number

DATA VERIFICATION SERVICES [V]

Verify247 (Email)

Data Service Code: VE

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VE&email={email}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VE&email={email}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VE&email={email}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "email": "test@example.com",
                    "valid": "YES",
                  }
             ]
         }
    }
    

Verify247 (Email) will verify that each of your email address is properly formatted and there is a working mailbox associated with it.

Example HTTP Request URL:

For Single Email
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=VE&email={email}

For Multiple emails at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=VE

JSON BODY { "VE": [ {"email": "email1"}, {"email": "email2"}, ................ ................ {"email": "email20"}, ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=VE&p1={email1}&p2={email2}...&p20={email20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Verify247 (Email) data service. It's value is alphabet VE
email required Email you want to verify.
out optional json Api result format, Possible values json, xml, csv.
If you want to lookup validation information of multiple emails(upto 20) at once then there are two alternatives:

1) Multiple emails can be provided as json body of request data as {"VE":[{'email': "email1"}, {"email": "email2"}]} where 'VE' is data service code and email1, email2 are actual email you want to lookup information of

2) Instead of email as query parameter you can provide p1={email1}&p2={email2} &...p20={email20} up to 20 emails as get parameter.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
valid: Whether email is valid or not(Possible values: YES or NO
reason: It provides reason why phone is not valid
email: Provided Email

Verify247 (Postal Address)

Data Service Code: VA

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VA&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VA&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VA&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "valid": "YES",
                    "addr1": "9 Summer St Unit 202",
                    "addr2": "Franklin MA 02038-1492",
                    "predir": "",
                    "streetnum": "9",
                    "postdir": "",
                    "street": "Summer",
                    "street_suffix": "St",
                    "unit": "202",
                    "state": "MA",
                    "zip": "02038",
                    "zip4": "1492",
                    "PRUrbCode": "",
                    "county": "Norfolk",
                    "FIPS": "021",
                    "company_name": "",
                    "congress_dist": "04",
                    "areacode": "508",
                    "timezone": "EST",
                    "DPBC": "092"
                  }
             ]
         }
    }
    

Verify247 (Postal Address) verifies provided USA postal addresses and parses out to different address components.

Example HTTP Request URL:

For verification of single location
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=VA&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}

For verification of multiple location(up to 20) at once
Header of request must be set to application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=VA

JSON BODY { "VA": [ { "address": "street_address", "city": "city", "state": "two_letter_state_code", "zip": "zip" }, ......................... ......................... { "address": "street_address", "city": "city", "state": "two_letter_state_code", "zip": "zip" } ] }

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Verify247 (Postal Address) data service. It's value is alphabet VA
address required Street address of location.
city optional city of location.
state optional Two letter state code of location.
zip optional zip of location.
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
valid: Whether provided address info is valid, (Possible values: YES or NO
addr1: address line 1 of location
addr2: address line 2 of location
predir:
streetnum:
postdir:
street:
street_suffix:
unit:
state:
zip:
zip4:
PRUrbCode:
county:
FIPS:
company_name:
congress_dist:
areacode:
timezone:
DPBC:
api: Letter code of Api requested, When performing multiple Api request it helps to separate whether current result is return of which API
status: Outcome of api request, useful only when performing multiple api request. It tells us about whether outcome of api reresented by api key was successful or not.

Verify247 (Phone Number)

Data Service Code: VP

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VP&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VP&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=VP&phone={phone}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "active": "YES",
                    "phone": "+134567.."
                    "confidence": "high"
                  }
             ]
         }
    }
    

Verify247 (Phone Number) will verify that each of the provided phone is active or not.

Example HTTP Request URL:

For Single Phone
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=VP&phone={phone}

For Multiple phones at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=VP&phone={phone}

JSON BODY { "VP": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"}, ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=VP&p1={phone1}&p2={phone2}...&p20={phone20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Verify247 (Phone Number) data service. It's value is alphabet VP
phone required Phone you want to verify.
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
active: Whether phone is active or not(Possible values: YES or NO
confidence: Confidence level of phone(Possible values: high or low
phone: Provided phone

DATA APPEND SERVICES [A]

Append247 (Phone)

Data Service Code: AP

    GET/POST Request 
    
        https://api.data247.com/v3.0?key={my_api_key}&api=AP&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}
    
    
    GET/POST Request 
    
        https://api.data247.com/v3.0?key={my_api_key}&api=AP&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}
    
    
    GET/POST Request 
    
        https://api.data247.com/v3.0?key={my_api_key}&api=AP&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "phone": "1234..",
                    "type": "Landline",
                    "firstname": "firstname",
                    "lastname": "lastname",
                    "address": "address",
                    "city": "city",
                    "state": "TX",
                    "zip": "1234",
                    "addtl": [
                        {
                            "phone": "123456",
                            "type": "Landline"
                        },
                        {
                            "phone": "123456",
                            "type": "Landline"
                        }
                     ]
                 }
             ]
         }
    }
    

Append247 (Phone) appends phone number for your contacts. You supply names and addresses of your contacts, and api will return their phone.

Example HTTP Request URL:

For Phone Append of One person
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=AP&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}

For Phone Append of Multiple people(upto 20) at once
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=AP

JSON BODY { "AP": [ { "firstname": "{firstname}", "lastname": "{lastname}", "address": "{address}", "city": "city", "state": "state", "zip": "zip" }, ......................... ......................... { "firstname": "{firstname}", "lastname": "{lastname}", "address": "{address}", "city": "city", "state": "state", "zip": "zip" } ] }

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Phone Append data service. It's value is alphabet AP
firstname required (only if address not provided) Firstname of person
lastname required (only if address not provided) Lastname of person
address required (only if firstname/lastname not provided) Street address of person
city optional City of person
state optional Two letter state code
zip optional Zip code
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
phone: Found phone number
type: Type of phone number(Landline/Mobile)
addtl: Additional numbers found, it will contain two data phone and type
In addition other provided parameters such as firstname, lastname, address are also returned

Append247 (Email)

Data Service Code: AE

    GET/POST Request 
    
        https://api.data247.com/v3.0?key={my_api_key}&api=AE&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}
    
    
    GET/POST Request 
    
        https://api.data247.com/v3.0?key={my_api_key}&api=AE&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}
    
    
    GET/POST Request 
    
        https://api.data247.com/v3.0?key={my_api_key}&api=AE&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "email": "test@test.com",
                    "firstname": "firstname",
                    "lastname": "lastname",
                    "address": "address",
                    "city": "city",
                    "state": "TX",
                    "zip": "1234"
                 }
             ]
         }
    }
    

Append247 (Email) appends email addresses for your contacts. You supply names and addresses or their phone numbers, and api will return their email addresses.

Example HTTP Request URL:

For Email Append of One person
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=AE&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}

For Email Append of Multiple people
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=AE

JSON BODY { "AE": [ { "firstname": "{firstname}", "lastname": "{lastname}", "address": "{address}", "city": "city", "state": "state", "zip": "zip" }, ......................... ......................... { "firstname": "{firstname}", "lastname": "{lastname}", "address": "{address}", "city": "city", "state": "state", "zip": "zip" } ] }

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Phone Append data service. It's value is alphabet AE
firstname required (only if address not provided) Firstname of person
lastname required (only if address not provided) Lastname of person
address required (only if firstname/lastname not provided) Street address of person
city optional City of person
state optional Two letter state code
zip optional Zip code
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
email: Found email
In addition other provided parameters such as firstname, lastname, address are also returned

Append247 (Reverse Phone)

Data Service Code: APR

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=APR&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=APR&phone={phone_number}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=APR&phone={phone_number}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "phone": "1234..",
                    "firstname": "xyz..",
                    "lastname": "lastname..",
                    "m_initial": "",
                    "suffix": "",
                    "business": "",
                    "address": "1234..",
                    "city": "1234..",
                    "state": "1234..",
                    "zip": "1234..",
                    "zip4": "1234..",
                    "dnc": "1234..",
                    "addrtype": "residental",
                    "gender": "M",
                    "gender_prcnt": "100"
                 }
             ]
         }
    }
    

Append247 (Reverse Phone) finds the name and address associated with a phone number.

Example HTTP Request URL:

For Single Phone
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=APR&phone={phone_number}

For Multiple Phones at once
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=APR

JSON BODY { "APR": [ {"phone": "{phone1}", {"phone": "{phone2}", ................ ................ {"phone": "{phone20}", ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=APR&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Append247 (Reverse Phone) data service. It's value: APR
phone required Phone number you want to look up address information of.
out optional json Api result format, Possible values json, xml, csv.
If you want to lookup address information of multiple phones(upto 20) at once then there are two alternatives:

1) Multiple phones can be provided as json body of request data as {"APR":[{'phone': "phoneNumber1"}, {"phone": "phoneNumber2"}]} where 'C' is data service code and phoneNumber1, phoneNumber2 are actual phone numbers you want to lookup carrier information of

2) Instead of phone as query parameter you can provide p1={phone1}&p2={phone2} &...p20={phone20} up to 20 phone numbers as get parameter.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
phone: provided phone number
firstname: provided phone number
lastname: provided phone number
m_initial:
suffix:
business:
address:
city:
state:
zip:
zip4:
dnc:
addrtype: address type such as residential
gender: M or F
gender_prcnt: probability percentage of gender (0-100)

Append247 (Reverse Email)

Data Service Code: AER

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AER&email={email}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AER&email={email}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AER&email={email}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "firstname:": "xyz..",
                    "lastname:": "lastname..",
                    "m_initial:": "",
                    "business": "",
                    "email": "",
                    "phone": "",
                    "phone_type": "",
                    "phone_telco_name": "",
                    "address": "",
                    "city": "",
                    "state": "",
                    "zip": "zip code",
                    "zip4": "zip4 code",
                    "house": "house number",
                    "predir": "",
                    "street": "street",
                    "street_type": "St",
                    "postdir": "",
                    "apt_type": "",
                    "aptno": "apt number"
                 }
             ]
         }
    }
    

Append247 (Reverse Phone) finds the name and address associated with a phone number.

Example HTTP Request URL:

For Single Email
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=AER&email={email}

For Multiple Emails at once
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=AER

JSON BODY { "AER": [ {"email": "email1"}, {"email": "email2"}, ................ ................ {"email": "email20"}, ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=AER&p1={email1}&p2={email2}...&p20={email3}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Append247 (Reverse Email) data service. It's value: AER
email required Email
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
firstname, lastname, m_initial: Middle initial of name
business: Business Name, email, phone, phone_type:L(Land Line), V(Voip), W(Wireless), O(Other) , phone_telco_name: telephone company provider, address, city, state, zip, zip4: zip+4 code, house: House Number, predir: Street Pre direction(N, S, W, WE etc), street, street_type: Street suffix, postdir: street post direction, apt_type: Apartment type, aptno: Apartment number

Append247 (Profile Data)

Data Service Code: AR

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AR&firstname={first_name}&lastname={last_name}&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AR&firstname={first_name}&lastname={last_name}&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AR&firstname={first_name}&lastname={last_name}&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}
    
    

The above request returns JSON structured like this:

 {
  "response": {
    "status": "OK",
    "results": [
      {
        "Identity": {
          "Name": {
            "FName": "ABC",
            "LName": "CDEF",
            "MName": "",
            "BusName": ""
          },
          "Address": {
            "House": "24",
            "PreDir": "",
            "Street": "Stree",
            "StrType": "WAY",
            "PostDir": "",
            "AptType": "",
            "AptNbr": "",
            "City": "FRANKLIN",
            "State": "MA",
            "Zip": "02038",
            "Z4": "3141",
            "DPC": "242",
            "CRTE": "R005",
            "CNTY": "",
            "Z4Type": "S",
            "DPV": "Y",
            "Deliverable": "Y",
            "ValDate": "201307"
          },
          "Phones": {
            "Phone": {
              "Phone": "7818640108",
              "PhoneType": "W",
              "DID": "",
              "RecType": "R",
              "IDate": "20040217",
              "ODate": "20190129",
              "TelcoName": "SPRINT SPECTRUM L.P.",
              "PHV": "2",
              "DACode": "",
              "Score": "200",
              "Category": "H"
            },
            "Phone2": {
              "Phone": "1234567",
              "PhoneType": "W",
              "DID": "",
              "RecType": "R",
              "IDate": "20110115",
              "ODate": "20110115",
              "TelcoName": "NEW CINGULAR WRL DC",
              "PHV": "5",
              "DACode": "D",
              "Score": "200",
              "Category": "H"
            },
            "Phone3": {
              "Phone": "",
              "PhoneType": "",
              "DID": "",
              "RecType": "",
              "IDate": "",
              "ODate": "",
              "TelcoName": "",
              "PHV": "",
              "DACode": "",
              "Score": "",
              "Category": ""
            }
          },
          "Emails": {
            "Email": {
              "Email": "",
              "Suppression": "",
              "Score": "",
              "Category": "",
              "Url": "",
              "ODate": ""
            },
            "Email2": {
              "Email": "",
              "Suppression": "",
              "Score": "",
              "Category": "",
              "Url": "",
              "ODate": ""
            },
            "Email3": {
              "Email": "",
              "Suppression": "",
              "Score": "",
              "Category": "",
              "Url": "",
              "ODate": ""
            }
          }
        },
        "PropertyAttributes": {
          "IDS": {
            "PID": "Y98711068157950",
            "AID": "Y000000131955272"
          },
          "Location": {
            "FIPSCD": "25021",
            "PROP_CENSUSTRACT": "4421022021",
            "PROP_MUNINAME": "FRANKLIN",
            "PROP_TOWNSHIPCD": "",
            "PROP_SUBDIVISION": "FORGE HILL CONDO",
            "PROP_ZONING": "",
            "PROP_RANGE": "",
            "PROP_SECTION": "",
            "PROP_LATITUDE": "42.08071",
            "PROP_LONGITUDE": "-71.42863",
            "PROP_LANDUSE": "112",
            "PROP_APN": "FRAN-000289-000000-000003-000036",
            "PROP_APNSEQNBR": "1"
          },
          "AdditionalInformation": {
            "PROP_OWNEROCC": "O",
            "PROP_ADDRIND": "S",
            "PROP_CORPIND": "",
            "PROP_RESCD": "Y",
            "PROP_IND": "11",
            "PROP_MOBHOME": "",
            "PROP_NRBBLD": "1",
            "PROP_STYLE": "TWN",
            "PROP_STORIESCD": "20",
            "PROP_STORIESNBR": "200",
            "PROP_APTNBR": "1",
            "PROP_QLTY": "",
            "PROP_BLDGCD": "",
            "PROP_BLDGIMPCD": "",
            "PROP_COND": "AVE",
            "PROP_CNSTRTYPE": "FRM",
            "PROP_EXTNW": "WDH",
            "PROP_VALCALC": "243000",
            "PROP_VAL_CALCIND": "A",
            "PROP_LAND_VALCALC": "",
            "PROP_LAND_VALCALC_IND": "A",
            "PROP_IMP_VALCALC": "243000",
            "PROP_IMP_VALCALC_IND": "A",
            "PROP_ASSED_VAL": "243000",
            "PROP_ASSED_LANDVAL": "",
            "PROP_ASSED_IMPVAL": "243000",
            "PROP_MRKTVAL": "",
            "PROP_MRKT_LANDVAL": "",
            "PROP_MRKT_IMPVAL": "",
            "PROP_APPRAISED_VAL": "",
            "PROP_APPRAISED_LANDVAL": "",
            "PROP_APPRAISED_IMPVAL": ""
          },
          "Attributes": {
            "PROP_VIEW": "",
            "PROP_LCTN_INFL": "",
            "PROP_FRONTFT": "",
            "PROP_DEPTHFT": "",
            "PROP_ACRES": "",
            "PROP_LANDSQFT": "",
            "PROP_YRBLD": "1983",
            "PROP_EFFYRBLD": "",
            "PROP_UNVBLDSQFT": "1645",
            "PROP_BLDSQFTIND": "L",
            "PROP_BLDSQFT": "",
            "PROP_LIVINGSQFT": "1645",
            "PROP_GRDFLRSQFT": "",
            "PROP_GROSSSQFT": "3087",
            "PROP_ADJGROSSSQFT": "",
            "PROP_BSMTSQFT": "800",
            "PROP_PRKGSQFT": "",
            "PROP_RMS": "4",
            "PROP_BEDRMS": "2",
            "PROP_BATHSCALC": "300",
            "PROP_BATHS": "300",
            "PROP_FULLBATHS": "2",
            "PROP_HALFBATHS": "1",
            "PROP_1QTRBATHS": "",
            "PROP_3QTRBATHS": "",
            "PROP_BATHFIXS": "",
            "PROP_AC": "",
            "PROP_BSMTF": "",
            "PROP_FRPL": "Y",
            "PROP_FRPLNBR": "1",
            "PROP_FRPLTYPE": "",
            "PROP_FND": "",
            "PROP_FLR": "",
            "PROP_FRAME": "",
            "PROP_GAR": "450",
            "PROP_HEAT": "FA0",
            "PROP_PRKGSPACES": "",
            "PROP_PRKGTYPE": "450",
            "PROP_POOL": "",
            "PROP_POOLCD": "",
            "PROP_ROOFCOVER": "2",
            "PROP_ROOFTYPE": "G",
            "PROP_ENERGY": "",
            "PROP_FUEL": "",
            "PROP_SEWER": "",
            "PROP_WATER": ""
          },
          "AssessorDeed": {
            "PROP_HOMESTEAD": "",
            "PROP_XMTVET": "",
            "PROP_XMT_DISABLED": "",
            "PROP_TAXAMT": "356000",
            "PROP_TAXYR": "2018",
            "PROP_DOCYR": "2011",
            "PROP_SALESDEEDCD": "G",
            "PROP_RECDATE": "20160531",
            "PROP_SELLERNAME": "CHRISTENSEN MOGENS V & JULIE M",
            "PROP_SALEDATE": "",
            "PROP_SALEAMT": "",
            "PROP_SALECD": "",
            "PROP_APNCD": "",
            "PROP_APNCNT": "",
            "PROP_ASMTYR": "2018",
            "PROP_SALESTRANSCD": "9"
          },
          "PriorSale": {
            "PROP_RECDATE_PRIOR": "20011001",
            "PROP_SALEDATE_PRIOR": "",
            "PROP_SALEAMT_PRIOR": "249400",
            "PROP_SALECD_PRIOR": "F",
            "PROP_APNCD_PRIOR": "",
            "PROP_DEEDCD_PRIOR": "MG",
            "PROP_DOCYR_PRIOR": "",
            "PROP_DEEDTYPE_PRIOR": "",
            "PROP_SALESTRANSCD_PRIOR": "1",
            "PROP_MTGAMT_PRIOR": "236900"
          },
          "Mortgage": {
            "PROP_MTGINTCD": "",
            "PROP_OWNERCD": "TR",
            "PROP_SELLCARRYBACK": "",
            "PROP_TITTLECOMPANY": "",
            "PROP_LOANTOVAL": "",
            "PROP_MTGAMT": "237956",
            "PROP_MTGDATE": "20110404",
            "PROP_MTGLOANCD": "FHA",
            "PROP_MTGDEEDCD": "MG",
            "PROP_MTGTERM": "30",
            "PROP_MTGDUEDATE": "20410501",
            "PROP_MTGASSUMPTIONAMT": "",
            "PROP_LENDERNAME": "WELLS FARGO BK NA",
            "PROP_MTGREFICD": "",
            "PROP_RMSEQUITYCD": "",
            "PROP_MTGINTRATE": "",
            "PROP_MTGINTRATETYPE": "",
            "PROP_MTGAMT2": "",
            "PROP_MTGDATE2": "",
            "PROP_MTGLOANCD2": "",
            "PROP_MTGDEEDCD2": "",
            "PROP_MTGTERM2": "",
            "PROP_MTGDUEDATE2": "",
            "PROP_MTGASSUMPTIONAMT2": "",
            "PROP_LENDERNAME2": "",
            "PROP_MTGREFICD2": "",
            "PROP_RMSEQUITYCD2": "",
            "PROP_MTGINTRATE2": "",
            "PROP_MTGINTRATETYPE2": "",
            "PROP_MTGAMT3": "",
            "PROP_MTGDATE3": "",
            "PROP_MTGLOANCD3": "",
            "PROP_MTGDEEDCD3": "",
            "PROP_MTGTERM3": "",
            "PROP_MTGDUEDATE3": "",
            "PROP_MTGASSUMPTIONAMT3": "",
            "PROP_LENDERNAME3": "",
            "PROP_MTGREFICD3": "",
            "PROP_RMSEQUITYCD3": "",
            "PROP_MTGINTRATE3": "",
            "PROP_MTGINTRATETYPE3": ""
          }
        },
        "DemographicAttributes": {
          "IDS": {
            "PID": "Y98711068157950",
            "AID": "Y000000146886547",
            "HHID": "Y000000146886547ORENBERG"
          },
          "Demographics": {
            "Gender": "M",
            "Age": "48",
            "MedYrBld": "1971",
            "LOR": "10",
            "Homeowner": "H",
            "EHI": "C",
            "DwellType": "M",
            "Married": "M",
            "MobHome": "",
            "Pool": "",
            "FirePl": "",
            "SglParent": "",
            "HHNBRSR": "",
            "CreditCard": "",
            "WealthScr": "",
            "CharityDnr": "",
            "MrktHomeVal": "",
            "Education": "",
            "Ethnicity": "",
            "ChildCd": "Y",
            "ChildAgeCd": "",
            "ChildNbrCd": "",
            "VehLux": "",
            "VehSuv": "",
            "VehTrk": "",
            "PctBlk": "T",
            "PctWht": "H",
            "PctHsp": "T",
            "PctAsi": "O",
            "PctEngSpeak": "K",
            "PctSpnSpeak": "T",
            "PctAsiaSpeak": "N",
            "PctSFDU": "",
            "PctMFDU": "A",
            "MHV": "F",
            "MOR": "K",
            "PctAuto": "A",
            "MedSchl": "162",
            "PctWhiteCollar": "K",
            "PctBlueCollar": "S",
            "PctOccO": "L",
            "DemoLvl": "1"
          },
          "LifeStyles": {
            "PIPriceClub": "",
            "PIWomanAprl": "",
            "PIMenAprl": "",
            "PIChildAprl": "",
            "PIPetAprl": "",
            "PIBookBuy": "",
            "PIBookRead": "",
            "PIHiTech": "",
            "PIArts": "",
            "PICollect": "",
            "PIHomeGrd": "",
            "PIHomeImp": "",
            "PICookWine": "",
            "PIGamble": "",
            "PITravel": "",
            "PIFitness": "",
            "PISelfImp": "",
            "PIAuto": "",
            "PISport": "",
            "PIOutdoor": "",
            "PIInvst": "",
            "PIBoat": "",
            "PIMoto": ""
          },
          "PowerScore": {
            "PurPowerScr": "",
            "ScoreCode": ""
          }
        },
        "PhoneAttributes": {
          "PhoneType": "",
          "PhoneType2": ""
        },
        "AutoAttributes": {
          "IDS": {
            "PID": "Y98711068157950",
            "AID": "Y000000199379061",
            "HHID": "Y000000199379061ORENBERG"
          },
          "Vehicle": {
            "Make": "KIA",
            "Model": "SOUL",
            "Year": "2011",
            "ClassCD": "CROSSOVER",
            "FuelTypeCD": "G",
            "MFGCD": "L",
            "StyleCD": "WAGON",
            "Mileages": "",
            "ODate": "20140929",
            "VIN": "KNDJT2A24B7286064"
          },
          "Vehicle2": {
            "Make": "",
            "Model": "",
            "Year": "",
            "ClassCD": "",
            "FuelTypeCD": "",
            "MFGCD": "",
            "StyleCD": "",
            "Mileages": "",
            "ODate": "",
            "VIN": ""
          },
          "Vehicle3": {
            "Make": "",
            "Model": "",
            "Year": "",
            "ClassCD": "",
            "FuelTypeCD": "",
            "MFGCD": "",
            "StyleCD": "",
            "Mileages": "",
            "ODate": "",
            "VIN": ""
          },
          "Vehicle4": {
            "Make": "",
            "Model": "",
            "Year": "",
            "ClassCD": "",
            "FuelTypeCD": "",
            "MFGCD": "",
            "StyleCD": "",
            "Mileages": "",
            "ODate": "",
            "VIN": ""
          }
        },
        "IPAttributes": {
          "IP": "",
          "IPRegion": "",
          "City": "",
          "Zip": "",
          "Latitude": "",
          "Longitude": "",
          "ISP": "",
          "IPFrom": "",
          "IPTo": ""
        }
      }
    ]
  }
} 

Our Append247 (Profile Data) service gives you additional information about the people on your lead list, including Financial, Interests, and/or Household data.

Example HTTP Request URL:

For Profile Data lookup of Single Person
https://api.data247.com/v3.0?key={my_api_key}&api=AR&firstname={first_name}&lastname={last_name}&address={street_address}&city={city}&state={two_letter_state_code}&zip={zip}

For Profile Data lookup of Multiple People(upto 20) at once
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=AR

JSON BODY { "AR": [ { "firstname": "first_name", "lastname": "last_name", "address": "street_address", "city": "city", "state": "state", "zip": "zip" }, ................ ................ { "firstname": "first_name", "lastname": "last_name", "address": "street_address", "city": "city", "state": "state", "zip": "zip" } ] }

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Append247 (Profile Data) data service. It's value: AR
firstname required firstname
lastname required lastname
address required address
city required city
state required state
zip required zip
phone optional Phone number if available.
email optional Email if available.
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request, results are grouped in to following category

Identity

Output Field Description Return Values
FNameAppended First Name20 characters
LNameAppended Last Name20 characters
MNameAppended Middle Initial1 Character
BusNameAppended Business Name100 Characters
HouseAppended Primary House Number10 Characters
PreDirAppended Street Pre Direction: N, S, E, W, NE, SW, etc2 Characters
StreetAppended Street name28 Characters
StrType Appended Street suffix: ST, AVE, BLVD, etc 4 Characters
PostDirAppended Street Post Direction: N, S, E, W, NE, SW, etc. 2 Characters
AptTypeAppended Secondary Unit designator: Apt, Suite, etc 4 Characters
AptNbrAppended Secondary unit number: Apt #, Suite #, etc 8 Characters
CityAppended USPS City Name28 Characters
StateAppended USPS state abbreviation 2 Characters
ZipAppended numeric USPS zip code5 Characters
Z4Appended numeric USPS zip+44 Characters
DPCAppended Delivery point code with check digit3 Characters
CRTEAppended Carrier Route4 Characters
CNTYAppended FIPS county code3 Characters
Z4Type Appended USPS Zip+4 type
F – firm or company address
G – General delivery address
H – High-rise or business complex
P – PO Box address
R – Rural route address
S – Street or residential address
Blank - Unknown
F, G, H, P, R, S
DPVAppended Delivery Point Validation
Y – Address DPV confirmed for both primary and (if present) secondary numbers
D – Address DPV confirmed for primary number only, secondary number information was missing
S – Address DPV confirmed for the primary number only, and secondary number information was present but unconfirmed
N – Both Primary and (if present) Secondary number information failed to DPV confirm
Blank – Address not presented to hash table
Y, D, S, N
DeliverableAppended Deliverable flag Y, N, or Blank
ValDateAppended Last address validation dateYYYYMMDD
Additional Contact Information:
PhoneAppended Phone (up to 3 additional Phones) 10 characters
PhoneType Appended Phone Type (up to 3, one for each appended phone)
L – Land Line, V - VoIP, W – Wireless, O - Other
L, V, W, O
Category Appended Matched Category (up to 3, one for each appended phone)
I – Individual
H – Household
A – Address
Z – Name/Zip
I, H, A, Z
EmailAppended Email (up to 3 additional Emails) 100 Characters
Suppression Email Suppression Code
D - Files with domains only
C - Cops
B - Bounce
T - Traps
O - Opt out
G - General
S - Complainers
I - other
N - None
D, C, B, T, O, G, S, I,N
Category Appended Matched Category (up to 3, one for each appended Email)
I – Individual, H – Household, A – Address, Z – Name/Zip
I, H, A, Z
Url Appended URL - Indicates the website the consumer "opted-in" to receive marketing emails. 100 Characters
ODate Appended Email Last Seen Date YYYYMMDD

Property Attributes:

Output Field Description Return Values
PROP_IND Property type indicator, 2 digit numeric:
10 = Single Family Residence / Townhouse
11 = Condominium (residential)
20 = Commercial
21 = Duplex, Triplex, Quadplex
22 = Apartment
23 = Hotel, Motel
24 = Commercial (condominium)
25 = Retail
26 = Services (general public)
27 = Office Building
28 = Warehouse
29 = Financial Institution
30 = Hospital (medical complex, clinic)
31 = Parking
32 = Amusement – Recreation
50 = Industrial
51 = Industrial Light>
52 = Industrial Heavy
53 = Transport
54 = Utilities
70 = Agricultural
80 = Vacant
90 = Exempt
nn
PROP_VALCALC The “total” (i.e., land + improvement) value closet to current market value used for assessment by county or local taxing authorities. Integer (dollars)
PROP_IMP_VALCALC The “improvement” value closest to current market value used for assessment by county or local taxing authorities. Integer (dollars)
PROP_IMP_VALCALC_IND The “improvement” value indicator
A = Assessed
M = Market
P = Appraised
T = Transitional
A, M, P, or T
PROP_ASSED_VAL The Total Assessed Value of the Parcel's Land & Improvement values as provided by the county or local taxing/assessment authority. Integer (dollars)
PROP_ACRES Total land mass in acres. (4 decimal points). Example: 13000=1.3 acres. Integer
PROP_LANDSQFT Total land mass in Square Feet. Integer
PROP_YRBLD The construction year of the original building. (e.g., YYYY). YYYY
PROP_LIVINGSQFT The area of a building that is used for general living. This is typically the area of a building that is heated or air conditioned and does not include Garage, Porch or Basement square footage. Integer
PROP_RMS Total number of rooms contained in the primary building. Integer
PROP_BEDRMS Total number of bedrooms contained in the primary building. Integer
PROP_BATHS Total number of bathrooms, 2 implied decimal places. 2.00 baths = 200. Integer
PROP_FULLBATHS Total number of Full Baths (typically comprised of a sink, toilet, and bathtub / shower stall). A home containing 2 1/2 baths would have the number 2 stored in this field. Integer
PROP_HALFBATHS Total number of Half Baths (typically comprised of a sink & toilet). A home containing 2 1/2 baths would have the number 1 stored in this field. Integer
PROP_AC The type of air conditioning method used to cool the building (e.g., Central, Wall Unit, Evaporative):
0=AC.NONE
ACA = AC.COMMERCIAL A/C
ACE = AC.CENTRAL
ACH = AC.CHILLED WATER
ACP = AC.CENTRAL PARTIAL
ACW = AC.CENTRAL & UNIT
ADU = AC.DUAL UNIT
AEV = AC.EVAPORATIVE
AF = AC.FAN COOLING
AHT = AC.HEAT PUMP
AOF = AC.OFFICE ONLY
APF = AC.REFRIGERATION
APK = AC.PACKAGE
APR = AC.PACKAGE ROOF
APT = AC.PARTIAL
APV = AC.REFRIGERATION / EVAPORATION
ASE = AC.SEPARATE SYSTEM
ASO = AC.SOLAR
ASP = AC.SPLIT SYSTEM
AWA = AC.WALL UNIT
AWI = AC.WINDOW UNIT
AWN = AC.WALL/WINDOW UNIT
nnn
3 characters)
PROP_FRPL This field is populated with a "Y" if a fireplace is located within the building. Y or blank
PROP_POOL Populated with a "Y" if a Pool is present on the parcel. Y or blank
PROP_ROOFTYPE 999 = BYPASS
9A0 = IRREGULAR
9B0 = LEAN TO
A = A-FRAME
B = BARN
C = CANOPY
D = DORMER
E = FRAME
F = FLAT
G = GABLE
H = GABLE/HIP>
I = HIP
J = GEODESIC
K = MANSARD
L = BARREL
M = MONITOR
N = CONTEMPORARY
O = SHED
P = PITCHED
Q = PYRAMID
R = ARCHED
S = SAWTOOTH
T = CATHEDRAL / CLERESTORY
U = BUBBLE
V = GAMBREL
W = SWISS CHALET / ALPINE
X = COMPLEX/CUSTOM
Y = BUTTERFLY
Z = GAMBREL / MANSARD
nnn
(3 characters)
PROP_TAXAMT The tax amount provided by the county or local taxing / assessment authority Integer (dollars)
PROP_RECDATE The date the sales transaction was record at the county YYYYMMDD
PROP_SALEAMT Price of the sale as depicted on the recorded sales transaction. Integer (dollars)
PROP_MTGAMT Amount of loan. Integer (dollars)
PROP_MTGDATE Date mortgage was initiated. YYYYMMDD
PROP_MTGTERM The length of time of the mortgage in years. Integer (years)
PROP_MTGDUEDATE Date mortgage becomes due. YYYYMMDD

Auto Attributes: Up to 4 vehicles.

Output Field Description Return Values
Make Vehicle Make, 30 characters max. String value
Model Vehicle Model, 30 characters max. String Value
Year Vehicle Year YYYY
ClassCD Vehicle Class Code, 15 characters max. 15 characters
FuelTypeCD Vehicle Fuel Code 1 character
MFGCD Vehicle Manufacturing Code 1 character
StyleCD Vehicle Style Code 10 characters
Mileage Mileage from the last odometer reading in increments of 10,000. A=0-10,000. Z= 250,000+. A-Z
ODate Last verification date. YYYYMMDD
IN_financing_prob_rank In Market for new Financing
100 - most qualified 10 - least qualified 0 - Unknown 0-100 IN_insurance_prob_rank In Market for getting Vehicle Insurance 100 - most qualified 10 - least qualified 0 - Unknown
0-100
IN_new_vehicle_prob_rank In Market for new Vehicle
100 - most qualified
10 - least qualified
0 - Unknown
0-100
IN_auto_parts_prob_rank In Market for buying auto parts
100 - most qualified
10 - least qualified
0 - Unknown
0-100
IN_used_vehicle_prob_rank In Market for used Vehicle
100 - most qualified
10 - least qualified
0 - Unknown
0-100

Phone Attributes:

Output Field Description Return Values
PhoneType Phone type for the Phone. L=Landline, V=VoIP, W=Wireless, O=Other. L, V, W, O
Phonetype2 Phone type for the 2nd Phone. L=Landline, V=VoIP, W=Wireless, O=Other. L, V, W, O

IP Attributes:

Output Field Description Return Values
IP IP v4 address. xxx.xxx.xxx.xxx IP v4 address
IPRegion Region. State name if within the US. 50 characters
City Approximate city the IP address is located within. 28 characters
LatitudeApproximate latitude of the IP address. 11 characters
Longitude Approximate longitude of the IP address. 11 characters
Zip Approximate Zip code associated with the IP address. 5 characters
ISP Internet service provider responsible for the IP address 255 characters
IPFrom Starting IP of the range that the IP address belongs xxx.xxx.xxx.xxx IP v4 address
IPTo Final IP of the range that the IP address belongsxxx.xxx.xxx.xxx IP v4 address

Demographic Attributes:

Output Field Description Return Values
GenderM=male, F=Female, blank or U=unknown. M, F, or U
Age Adult Age. 0 - 99
LOR Length of Residence in years, 2 digits. 00 - 99
Homeowner H=Homeowner, R=Renter, A = Inferred Homeowner, B = Inferred Renter H, R, A or B
MedYrBld The year home was built. 4 digits. nnnn
EHI Estimated household income, 1 character:
A = Less than $20,000
B = $20,000 - $29,999
C = $30,000 - $39,999
D = $40,000 - $49,999
E = $50,000 - $74,999
F = $75,000 - $99,999
G = $100,000 - $124,999
H = $125,000 or more
A - I
Married M=Married, S=Single, A=Inferred Married, B=Inferred Single. M, S, A, or B
WealthScr Model based on income, homeownership, and other assets owned:
A = Estimated Net less than $5,000 B = Estimated Net $5,000 - $19,999 C = Estimated Net $20,000 - $49,999 D = Estimated Net $50,000 – $79,999 E = Estimated Net $80,000 - $99,999 F = Estimated Net $100,000 - $249,999 G = Estimated Net $250,000 - $499,999 H = Estimated Net over $500,000
A - H
DwellType Dwelling Type. S=Single Family Dwelling Unit (SFDU). M=Multi-family Dwelling Unit (MFDU). S or M
MrktHomeVal Estimated Home Market value:
A = $1,000 - $24,999 B = $25,000 - $49,999 C = $50,000 - $74,999 D = $75,000 - $99,999 E = $100,000 - $124,999 F = $125,000 - $149,999 G = $150,000 - $174,999 H = $175,000 - $199,999 I = $200,000 - $224,999 J = $225,000 - $249,999 K = $250,000 - $274,999 L = $275,000 - $299,999 M = $300,000 - $349,999 N = $350,000 - $399,999 O = $400,000 - $449,999 P = $450,000 - $499,999 Q = $500,000 - $749,999 R = $750,000 - $999,999 S = $1,000,000+
A - S
ChildCd Presence of Children. Y= children present. Y or blank
ChildNbrCd Number of Children. A=No children, B=less than 3, C= 3-5 children. A – C
MHV Median House Value Code:
A = Less than $50,000 B = $50,000 - $99,999 C = $100,000 - $149,999 D = $150,000 - $249,999 E = $250,000 - $349,999 F = $350,000 - $499,999 G = $500,000 - $749,999 H = $750,000 - $999,999 I = $1,000,000+
A – I
MedSchl Median years of school, 3 digits max. 0 - 999
PurPowerScrPurchasing Power Model, 1 character:
A = (820-High)
B = (800-819)
C = (780-799)
D = (760-779)
E = (740-759)
F = (720-739)
G = (700-719)
H = (680-699)
I = (660-679)
J = (640-659)
K = (620-639)
L = (600-619)
M = (580-599)
N = (560-579)
O = (540-559)
P = (520-539)
Q = (500-519)
R = (480-499)
S = (460-479)
T = (Low-459)
A - T

Append247 (Name)

Data Service Code: AN

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AN&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AN&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AN&phone={phone}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "name": "demo name",
                    "phone": "1234..",
                 }
             ]
         }
    }
    

Append247 (Name) takes phone as input and returns name of person behind it.

Example HTTP Request Url:

For Single Phone/Person
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=AN&phone={phone_number}

For Multiple Phones/People upto 20 phones at once
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=AN

JSON BODY { "AN": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"}, ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=AN&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Append247 (Name) It's value: AN
phone required Phone number you want to look up name of person behind it.
out optional json Api result format, Possible values json, xml, csv.
If you want to lookup for multiple phones(upto 20) at once then there are two alternatives:

1) Multiple phones can be provided as json body of request data as {"AN":[{'phone': "phoneNumber1"}, {"phone": "phoneNumber2"}]} where 'AN' is data service code and phoneNumber1, phoneNumber2 are actual phone numbers you want to lookup carrier information of

2) Instead of phone as query parameter you can provide p1={phone1}&p2={phone2} &...p20={phone20} up to 20 phone numbers as get parameter.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
name: Name of person who owns provided phone
phone:Provided phone

Append247 (Gender)

Data Service Code: AG

Coming Soon!

Append247 (Zipcode)

Data Service Code: AZ

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AZ&zip={zip}&plus4=zip+4code
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AZ&zip={zip}&plus4=zip+4code
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=AZ&zip={zip}&plus4=zip+4code
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
            {
                "addr1": "Address line 1",
                "addr2": "Address line 2",
                "predir": "",
                "streetnum": "",
                "postdir": "",
                "street": "Street Addresss",
                "street_suffix": "",
                "unit": "",
                "city": "Denver",
                "state": "CO",
                "zip": "80201",
                "zip4": "",
                "PRUrbCode": "",
                "county": "Denver",
                "FIPS": "031",
                "company_name": "",
                "congress_dist": "",
                "areacode": "303",
                "timezone": "MST",
                "DPBC": ""
            }
          ]
        }
    }

Append247 (Zipcode) takes zip of location and returns formatted address components(address1, city, state etc) of that location.

Example HTTP Request Url:

For Single Zip
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=AZ&zip={zip}&plus4=zip+4code

For Multiple Zips upto 20 phones at once
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=AZ

JSON BODY { "AZ": [ { "zip": "1234", "plus4": "" }, ................ ................ { "zip": "1234", "plus4": "" } ] }

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Append247 (Name) It's value: AN
zip required zip code of location
plus4 optional zip+4 code of location
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
addr1, addr2, predir, streetnum, postdir, street, street_suffix, unit, city, state, zip, zip4, PRUrbCode, county, FIPS, company_name, congress_dist, areacode, timezone, DPBC

GEOLOCATION SERVICES [G]

Locate247 (IP)

Data Service Code: GI

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=GI&ip={ip}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=GI&ip={ip}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=GI&ip={ip}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "ip_address": "123.656...",
                    "city": "city",
                    "state": "state",
                    "country": "united states",
                    "zipcode": "1234",
                    "latitude": 42.33704,
                    "longitude": -71.07203,
                    "areacode": "617",
                    "timezone": -5,
                    "dst": ""
                }
             ]
         }
    }
    

Locate247 (IP) returns the geolocation data for IP addresses.

Example HTTP Request Url:

For Single IP
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=GI&ip={ip}

For Multiple IPs at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=GI

JSON BODY { "GI": [ {"ip": "ip1"}, {"ip": "ip2"}, ................ ................ {"ip": "ip20"}, ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=GI&p1={ip1}&p2={ip2}...&p20={ip20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for Locate247 (IP) data service. It's value is GI
ip required Ip v4 address.
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
ip_address, city, state, country, zipcode, latitude, longitude, areacode timezone, dst

REGULATORY SERVICES [D]

Do-Not-Call (USA)

DNC Check

Data Service Code: DC

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DC&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DC&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DC&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DC&phone={phone}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                  "phone": "12345656",
                  "dnc": "FEDERAL DNC"
                }
            ]
        }
    }

DNC Check returns whether a phone number exists in your internal dnc list OR in Federal Do-Not-Call list. In order to use Federal Do-Not-Call service, you need to open an account with us and then go to https://telemarketing.donotcall.gov (the FTC's National Do Not Call Registry) and register with them. After you have registered with the FTC, you will need to specify the Area Codes that you will be calling. The first five Area Codes are free; after that, the FTC will charge you for each Area Code. Once you have selected your Area Codes, you will be assigned an Organization ID and a Subscription Account Number (SAN). You will need to give us both of these numbers in order for us to allow you to legally access our Do-Not-Call Service. You can open a Help Desk ticket on our website and send us those two pieces of information. We will update your account and notify you that you are good to go.

Example HTTP Request URL:

For Single Phone DNC Lookup
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=DC&phone={phone_number}

For Multiple Phones at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=DC

JSON BODY { "DC": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"} ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=DC&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Query Parameters

Parameter Required? Default Description
key required Your api key used for authentication
api required Letter code for DNC Check It's value: DC
phone required Phone number you want to check whether it exists in Federal Do-Not-Call list.
out optional json Api result format, Possible values json, xml, csv.

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
dnc: It tells whether provided phone exists in DNC List.
Possible values: OK-TO-DIAL(phone doesnot exists in any kind of DNC list and is ok to dial) , FEDERAL DNC (phone exists in Federal Do-Not-Call list), INTERNAL DNC (phone exists in your internal DNC list), UNAUTHORIZED (you are not authorized to check phone againist Federal DNC List, either you donot have permission for provided areacode or your subscribtion expired or account inactive),
phone: provided phone

DNC Add

Data Service Code: DA

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DA&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DA&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DA&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DA&phone={phone}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "api": "DA",
                    "status": "OK",
                    "phone": "1234..",
                    "action": "ADDED"
                   }
             ]
         }
    }
    

Using DNC Add DA service, you can add phone to your own internal dnc list.

Example HTTP Request Url:

For Single Phone
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=DA&phone={phone_number}

For Multiple Phones at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=DA

JSON BODY { "DA": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"} ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=DA&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
action It tells whether provided phone added to internal DNC list, Possible values: ADDED
phone:Provided phone
api: Letter code of Api requested
status: Outcome of api request

DNC Remove

Data Service Code: DR

    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DR&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DR&phone={phone}
    
    
    GET/POST Request 
    
    https://api.data247.com/v3.0?key={my_api_key}&api=DR&phone={phone}
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "api": "DR",
                    "status": "OK",
                    "phone": "1234..",
                    "action": "REMOVED"
                   }
             ]
         }
    }
    

Using DNC Remove DR service, you can remove phone from your internal dnc list.

Example HTTP Request Url:

For Single Phone
GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=DR&phone={phone_number}

For Multiple Phones at once upto 20
Header of request must be set application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=DR

JSON BODY { "DR": [ {"phone": "phone1"}, {"phone": "phone2"}, ................ ................ {"phone": "phone20"} ] }

OR

GET/POST https://api.data247.com/v3.0?key={my_api_key}&api=DR&p1={phone_number1}&p2={phone_number2}...&p20={phone_number20}

Response Parameters

If API request is successful status key value will be OK otherwise it takes value of one of listed error codes below

For successful API request following parameters are returned in result
action It tells whether provided phone removed from internal DNC list, Possible values: REMOVED
phone:Provided phone
api: Letter code of Api requested
status: Outcome of api request

Do-Not-Call (Canada)

COMING SOON!

FRAUD DETECTION SERVICES [P]

Trust247 (User Identity)

Data Service Code: PI

COMING SOON!

Multiple API Request

    GET/POST Request 
        
    https://api.data247.com/v3.0?key={my_api_key}&api=AP,MT&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip} 
    
    
    GET/POST Request 
        
    https://api.data247.com/v3.0?key={my_api_key}&api=AP,MT&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip} 
    
    
    GET/POST Request 
        
    https://api.data247.com/v3.0?key={my_api_key}&api=AP,MT&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip} 
    
    

The above request returns JSON structured like this:

    {
        "response": {
            "status": "OK",
            "results": [
                {
                    "phone": "1234..",
                    "type": "Landline",
                    "firstname": "firstname",
                    "lastname": "lastname",
                    "address": "address",
                    "city": "city",
                    "state": "TX",
                    "zip": "1234",
                    "wless": "y",
                    "carrier_name": "Turkcell (Turk Telekom)",
                    "carrier_id": "9087",
                    "sms_address": "smsgateway@example.com",
                    "mms_address": "mmsgateway@example.com"
                 }
             ]
         }
    }
    

Now in version 3 of Data247 API you can perform multiple api request in sequence.
For example you may want to know phone number and also the SMS/MMS gateway addresses/carrier info associated with that number for certain contact, In such scenario you need to run both Phone Append and Text@ data service in sequence.
Multiple apis should be provided in comma separated form in order.

Request/Response examples for Multiple API request

1. Single Request Data(for eg; phone append/carrier lookup of single person
Request:
https://api.data247.com/v3.0?key={my_api_key}&api=AP,MT&firstname={firstname}&lastname={lastname}&address={address}&city={city}&state={state_code}&zip={zip}

Response:

{ "response": { "status": "OK", "results": [ { "phone": "1234567890", "type": "Landline", "firstname": "fnameee", "lastname": "lnameee", "address": "streeeet address", "city": "cityyyy", "state": "TX", "zip": "1234", "carrier_name": "AT+T Local", "carrier_id": "28287", "sms_address": "sms@test.com", "mms_address": "mms@test.com" } ] } }

2. Multiple Request Data(for eg; phone append/carrier lookup of more than one person
Request:

Header of request must be set to application/json
POST https://api.data247.com/v3.0?key={my_api_key}&api=AP,MT

JSON BODY { "AP": [ { "firstname": "{firstname1}", "lastname": "{lastname1}", "address": "{address1}", "city": "city1", "state": "state1", "zip": "zip1" }, { "firstname": "{firstname2}", "lastname": "{lastname2}", "address": "{address2}", "city": "city2", "state": "state2", "zip": "zip2" } ] }

Response:

{ "response": { "status": "OK", "results": [ { "status": "OK", "phone": "1234567890", "type": "Landline", "firstname": "firstname1", "lastname": "lastname1", "address": "address1", "city": "city1", "state": "state1", "zip": "zip1", "carrier_name": "AT+T Local", "carrier_id": "28287", "sms_address": "sms@test.com", "mms_address": "mms@test.com" }, { "status": "OK", "phone": "234567890", "type": "Landline", "firstname": "firstname2", "lastname": "lastname2", "address": "address2", "city": "city2", "state": "state2", "zip": "zip2", "carrier_name": "MT Telecom", "carrier_id": "5678", "sms_address": "sms2@test.com", "mms_address": "mms2@test.com" } ] } }

Note: Incase of mulptiple request each result block also contains status key(message key if error occurred) so you know whether outcome of each request data succed or not.

Errors

In addition to http error codes, Data247 API uses it's own error codes. They are listed elow:

Error Code Description
D247_INVALID_CREDENTIALS Wrong key value provided!
D247_ACCOUNT_INACTIVE Account set to inactive, possible reasons could be expired subdsription, not enough balance on account
D247_MISSING_REQUIRED_PARAMS Not all required parameters for specific api is provided or provided parameters are invalid.
D247_PROCESSING_ERROR Something unknown error occurred wrong while processing your request.
D247_INVALID_API Wrong api parameter value provided!
D247_NO_DATA_FOUND No related data found on our database.
D247_MISSING_PHONE_NUM Data service api you requested requires phone but you didn't provide it.
D247_INVALID_PHONE Data service api you requested requires phone but you didn't provide valid phone.
D247_INVALID_EMAIL Data service api you requested requires email but you didn't provide valid email.
D247_CANNOT_ADD_NUMBER The number you provided cannot be added to DNC list.
D247_CANNOT_REMOVE_NUMBER The number you provided cannot be removed from DNC list.

Examples

Here are some API examples in various other programming languages not listed in the pane to the right.

Don't see your language here? Let us know. Or, if you have a working example, we'd appreciate if you'd send it to us so we can add it here.

JAVA


Name this example test.java, fill-in the apikey variable, compile, and run!


import java.io.BufferedReader; import java.io.InputStreamReader; import java.net.HttpURLConnection; import java.net.URL; public class test { public static void main(String[] args) { try { String apikey = ""; URL url = new URL("https://api.data247.com/v3.0?key=" + apikey + "&api=MT&phone=17818640108"); HttpURLConnection conn = (HttpURLConnection) url.openConnection(); conn.setRequestMethod("GET"); conn.setRequestProperty("Accept", "application/json"); if (conn.getResponseCode() != 200) { throw new RuntimeException("Failed : HTTP Error code : " + conn.getResponseCode()); } InputStreamReader in = new InputStreamReader(conn.getInputStream()); BufferedReader br = new BufferedReader(in); String output = br.readLine(); System.out.println("Output = " + output); conn.disconnect(); } catch (Exception e) { System.out.println("Exception in example:- " + e); } } }

Perl

Requires REST::Client package. Don't forget to add your API key.


use REST::Client; my $client = REST::Client->new(); $content = {'Content-type' => 'application/json'}; $url="http://api.data247.com/v3.0"; $req = '{ "key" : "", "api" : "MT", "phone" : "17818640108" }'; $client->POST($url,$req,$content); print $client->responseContent();