Versium APIs enable real time access to LifeData®
Our API enables programmatic use of Versium’s LifeData® and Predictive Scoring services through a simple, RESTful API. JSON (default) and XML responses are provided. Both HTTP GET or HTTP POST are supported. Non-US data support is sparse and currently poorly supported. All character encodings are UTF-8, unless specified otherwise.
|basic||name, address, phone, dob|
|email address, ip, originating source, timestamp|
|auto||vehicle make, model, year, edition, trim, VIN|
|bus||business name, address, phone, contact name, title, sic, naics, years in business, annual sales, & more|
|finbasic||est wealth, credit rating, est income, est household income, net worth|
|fincredit||amex, mc, visa card holder, number of credit lines, averge size of credit line & more|
|finmort||home value, purchase date, lender name, interest rate, home age, a/c, pool, & more|
|eduocc||education level, occupation, years in school|
|demobasic||own/rent, gender, ethnicity, marital status, children present, language, religion & more|
|demodetail||investing, reading, music, electronics, collectibles, home improvement, lifestyles, travel, exercise, sports, pets & more|
|b2bemail||email address, title, business name, phone, address|
|rateip||quality of IP address (proxy, known bad, unreliable country etc)|
|bounce||whether or not email will bounce/report as spam.|
|npanxx||location, carrier, valid|
|socmap||email address, social network id & more
*note: as of June 2012, this uses ‘house data’ only; it is not a real time lookup.
|socrt||email address, social network id & more - real time social network lookup.
*note: as of September 2012, latency could be up to 5 seconds.
There are three types of “params”: output, configuration and query data. All configuration parameters are prefixed with “cfg_” and query parameters are prefixed with “d_”, while output is not prefixed.. output (default=’json’) -Specify JSON or XML output responses. cfg_compactor (default=1) -Record compactor will simplify record display by merging records which are very likely to be the same. Turning this feature off will increase the number of records output. cfg_recurse (default=0) -Record recursion (cfg_recurse=1) enables broad matching across widely varied data sources. This will lower overall match confidence, but can increase the number of possible matches. It is required for unusual data jumps (i.e. Social Net Handle to Vehicle VIN).
Additionally, cfg_recurse=2 enables a prematch and re-search. In this embodiment, the input query is first used to identify and score candidate matches against all eligble data sources. For example, a user may request social data by a phone number which does not exist in the social record (prodids=socmap only). cfg_recurse=2 will search across all sources with phone numbers to identify which record contains information that would be able to be used to search the socmap dataset and then performs this query cfg_bestmatchonly -This function scores all potential records that could be returned for a query and only returns back a single record which scored the highest.
When a match is returned, it will include three additional values:
|stats_#Recscore||This score is calculated based on weighted field matches. The higher the value, the more likely the record is a match for the query. Match quality within certain fields will have a larger impact in increasing this score. For example, a query on “DAVID” will have a higher score on “DAVID” than “DAVE” than “D”. Additionally, the MatchCodes (see below) will increase the overall value here.|
|stats_#RecScoreUnweighted||This score is calculated as above, except that the number of MatchCodes present will not impact the score.|
|stats_#MatchCode||Match Codes can be used to discern why a particular record was returned for a given query. Some, none or all match codes may be present in a result set, separated by commas.
There are several hundred different data query parameters. As a general rule of thumb, most queries will consist of at least one of Email, Phone, Street Address, SocNetID, and optionally one or more of a Business Name, Person Name, DOB, and/or City/State/Zip.
The popular ones are listed below:
|Parameter Name||Data Type|
|d_first||first name (‘Joe’)|
|d_last||last name (‘Smith’)|
|d_address||Full street address (‘1234 some street, suite 283’)|
|d_city||City name (‘seattle’)|
|d_state||State abbreviation (‘wa’)|
|d_zip||ZIP code (‘91981’)|
|d_email||Email address (‘firstname.lastname@example.org’)|
|d_phone||Phone number (‘6195798842’)|