The Demandbase Domain API takes a domain parameter as input and returns up to 43 validated firmographic data fields, among which are: 1) industry; 2) revenue; 3) isp (t/f); 4) address; 5) lat/long; and many more. Frequent uses of the API include: increasing conversion rates by enabling customized messaging, shortcutting user's paths to relevant content, streamlining measurement of responses to online campaigns, and reducing the number of required fields in web forms, increasing form fill rates.
The underpinning services work without cookies or personally identifiable identification (PII), instead relying on several proprietary methods to reliably build on the fundamental requirement to connect to the Internet, an IP address, to map a business up, across, and through the API.
The API outputs either XML or JSON data formats.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at email@example.com