contact info API

Implementation Guide

Introduction

Searchbug® Contact Info API allows you to find missing contact information for people and businesses in the US. The API returns person’s first and last name, business name, full address, phone number, and email address.

Sending Request

The request should be sent to Searchbug using the following URL using the POST method:

https://data.searchbug.com/api/search.aspx

Search Parameters

You can submit your request via:

  • POST Header: Parameters sent as custom headers
  • POST Body: Parameters sent as form-data
Parameter Value Example Description
CO_CODE 12345678 Required. Your account number
PASS 76162c80a0333c91 API Key or account password (not needed if using Bearer Token)
TYPE api_contact Required. Use "api_contact" for this API.
FNAME James First name
MNAME M Optional. Middle Name or Middle Initial
LNAME Baker Last name
CO_NAME Bulk Packing Company Name (the company you are searching for)
ADDRESS 200 E 69TH ST Street Address in postal format. Do not include unit number.
CITY MIAMI City of the residence
COUNTY Miami-Dade County of the residence or business (e.g. “San Bernardino”). State is required for search by country. Do not include city, when searching by county.
STATE FL State of the residence
ZIP 33101 Zip Code of the residence
PHONE 2127731234 Phone number. If the phone number is supplied, all other input parameters are ignored, and reverse phone search is performed.

The phone numbers can be in any format. They can contain spaces, dashes, parentheses, or periods. Examples: 212-773-1234, 2127731234, 212.773.1234, (212) 773-1234.
E_MAIL user@domain.com Email Address in a valid format. If the Email is supplied, all other input parameters are ignored, and a reverse email search is performed.

Not all records have email data. Reverse email searches may not always return the results.
DOB 12/28/1998 Optional. Date of birth (format: mm/dd/yyyy).
AGE 54 Optional. Age (numeric value)
FORMAT JSON Optional. The default is XML. To get results in JSON format, pass FORMAT=JSON
REF Client1 Optional. Used for API usage tracking per application or customer (100 char max).

Supported search input options

  • First and Last Name and Full Address
  • First and Last Name, County and State
  • First and Last Name, City and State
  • First and Last Name and State
  • First and Last Name only (if name is fairly unique)
  • Last Name and Full Address
  • Last Name, City and State
  • Full Street Address
  • Phone Number
  • Email Address
  • Business Name and Full Address
  • Business Name, County and State
  • Business Name, City and State
  • Business Name and State
  • Business Name and ZIP Code

You can add Age or Date of Birth as additional criteria for people name-based searches.

Receiving Results

The results may include one or multiple records (<RECORD>). Some information (e.g. Business Name, Phone, Email, DOB, Age) is not available for all records.

Below are examples of XML and JSON results. If data is missing for a particular field, empty tag will be sent (<EMAIL></EMAIL> or EMAIL: "")

  • SRC is SearchBug internal code that is used for troubleshooting
  • PHFND is indicator if the results contain at least one phone number
  • ADFND is indicator if the results contain at least one street address
  • EMFND is indicator if the results contain at least one email address

Example of XML results

                             

<RESULTS>
    <SRC>TRC</SRC>
    <PHFND>X</PHFND>
    <ADFND>X</ADFND>
    <EMFND/>X</EMFND>
    <RECORD>
        <FNAME>DAVID</FNAME>
        <MNAME>KUO</MNAME>
        <LNAME>WU</LNAME>
        </BNAME>
        <PHONES>
            <PHONE>(626) 333-8218</PHONE>
            <PHONE>(626) 271-0010</PHONE>
            <PHONE>(626) 369-9258</PHONE>
            <PHONE>(626) 968-2034</PHONE>
            <PHONE>(626) 968-5351</PHONE>
            <PHONE>(626) 446-2619</PHONE>
            <PHONE>(626) 446-8905</PHONE>
            <PHONE>(626) 395-9991</PHONE>
            <PHONE>(626) 968-2034</PHONE>
        </PHONES>
        <ADDRESSES>
            <ADDRESS>
                <STREET>6847 TOURMALINE DR</STREET>
                <CITY>EASTVALE</CITY>
                <COUNTY>RIVERSIDE</COUNTY>
                <STATE>CA</STATE>
                <ZIP>92880</ZIP>
            </ADDRESS>
        </ADDRESSES>
        <EMAILS>
                <EMAIL>DWU1@NETSCAPE.NET</EMAIL>
                <EMAIL>DAVIDWU@NETZERO.NET</EMAIL>
                <EMAIL>DWU@NETSCAPE.NET</EMAIL>
                <EMAIL>DAVIDW8818@SBCGLOBAL.NEET</EMAIL>
        </EMAILS>
        </DOB>
        <AGE>79</AGE>
    </RECORD>       
</RESULTS>

Here is an example of JSON results:

                        
{
    Status: "Success",
    - Data: 	{
        SRC: "TRC",
        PHFND: "X",
        ADFND: "X",
        EMFND: "X",
        RECORD: [
        - {
            FNAME: "DAVID",
            MNAME: "WU",            
            BNAME: null,
            PHONES: {
                PHONE: [
                "(626) 333-8218",
                "(626) 271-0010",
                "(626) 369-9258",
                "(626) 968-2034",
                "(626) 968-5351",
                "(626) 446-2619",
                "(626) 446-8905",
                "(626) 395-9991",
                "(626) 968-2034"
                ]
            },
            ADDRESSES: {
               ADDRESS: {
                    STREET: "6847 TOURMALINE DR",
                    CITY: "EASTVILLE",
                    COUNTY: "RIVERSIDE",
                    STATE: "CA",
                    ZIP: "92880"
                } 
            },
            EMAILS: {
                EMAIL: [
                    "DWU1@NETSCAPE.NET",
                    "DAVIDWU@NETEZERO.NET",
                    "DWU@NETSCAPE.NET",
                    "DAVIDW8818@SBCGLOBAL.NET"
                ]
            },
            DOB: null,
            AGE: "79"
        }
    },
          ERROR: null
  }

Example of No Results

                               
<?xml version="1.0" encoding="ISO-8859-1" standalone="true"?>
<RESULTS>
    <FOUND>NO</FOUND>
</RESULTS>

{
    STATUS: "NORESULTS",
    DATA: "",
    ERROR: ""
}

Error Example - wrong account or password

                                       
<?xml version="1.0" encoding="ISO-8859-1" standalone="true"?>
<RESULTS>
    <ERROR>PASSWORD OR ACCOUNT NUMBER ARE NOT VALID</ERROR>
</RESULTS>

{
    STATUS: "ERROR",
    DATA: "",
    ERROR: "PASSWORD OR ACCOUNT NUMBER ARE NOT VALID"
}

Checking API Prepaid Balance

To check your current prepaid balance, please use the following URL format over HTTPS. Use TYPE_API specific to the API type for which you want to get the stats. This example is for api_loc2. Use 'api_contact' for this API.

https://data.searchbug.com/api/search.aspx?CO_CODE=<AccountID>&PASS=<Password>&TYPE=STATUS&TYPE_API=api_loc2 

<RESULTS>
    <API_TYPE>api_loc2</API_TYPE>
    <API_NAME>API - Line Type and Carrier (Standard)</API_NAME>
    <DAILY>1</DAILY>
    <MONTHLY>4</MONTHLY>
    <RATE>0.0100</RATE>
    <BALANCE>47.72</BALANCE>
    <PREPAID>100.00</PREPAID>
    <DATE>01/12/2023</DATE>
</RESULTS>

For further technical details and customer support, please chat with us, email us, or call us (800) 990-2939.

For sales and pricing information please contact sales@searchbug.com.