How XML Data Integration Works

As a web-based service accessed with an XML interface, API411® integrates easily into applications regardless of the programming language or model used.

An application initiates the API411 service with an HTTP GET request, using an IP address that is authenticated for access with W3 Data. The URL access consists of the server name, servlet path, and a list of parameters. You control the types of searches you want to perform with the parameter set specified on the HTTP request. You can specify which data sets you want to search, and request optional demographic information about a residence or business.

For example, the following query initiates a Reverse ZIP Code search, requesting the city and state for a specific ZIP code (parameter field titles are listed in bold):

http://enterprise.w3data.com/directaccess?ver=2.0&type=rz&z=98101

The Reverse ZIP Code search request above returns the following data:
code snippet
In another example, the diagram below shows a sample data flow for a residential Reverse Phone search. Note that you can easily combine the use of API411 with other, internal data sources. If a search returns many listings, a pagination option controls how many listings are displayed per page.

SAMPLE DATA FLOW

  1. Application passes a phone number.

  2. Application checks the customer database and does not find the number.

  3. Application sends a request to the API411 service.

  4. API411 returns name, address, latitude/longitude, carrier information, phone type and optional demographics.

  api411 data flow chart

API411 provides ways to extend the search if no match is found on the first pass. Even if the complete information isn't available, API411 returns useful information. For example, when complete information isn't available, a Reverse Phone search can still return information about the carrier, phone type and the city associated with the number.

Because API411 uses HTTP and XML data, implementation is rapid and requires no application infrastructure changes. Most customers find that the actual integration/implementation of API411 within their application is completed within a single day. Once the integration is complete, there is little ongoing administration or effort in maintaining the API411 integration.