Output Format

Currently, ZoomInfo supports two output formats: XML and JSON. If no output type is specified, output defaults to XML.

XML

You can request XML output in two different ways. One is to use the request parameter, OutputType. The other way is to use the HTTP request header, Accept.

To use the request parameter OutputType for XML output, construct the URL in the following way:

[API_URL]?[SEARCH_CRITERIA]&pc=PartnerCode&OutputType=xml&key=EncryptedKey

API_URL refers to the corresponding URL for the intended query. SEARCH_CRITERIA is part of the query string and contains the valid search parameters with values, such as firstName=name1&lastName=name2. Refer to the input parameter tables for each search query type. OutputType is a request parameter you use to specify the intended output format type.

Note: For XML, the OutputType parameter is optional. All the APIs default to XML.

JSON

You can request JSON output in two different ways. One is to use the request parameter,OutputType. The other way is to use the HTTP request header, Accept.

To use the request parameter OutputType for JSON output, construct the URL in the following way:

[API_URL]?[SEARCH_CRITERIA]&pc=PartnerCode&outputType=json&key=EncryptedKey

API_URL refers to the corresponding URL for the intended query. SEARCH_CRITERIA is part of the query string and contains valid searching parameters with values, such asfirstName=name1&lastName=name2. Refer to the input parameter table for the intended query. TheOutputType request parameter is used to specify the desired output type (JSON or XML).

HTTP Accept Request Header

The alternative way to specify output type is to include the output type information in the HTTP Acceptrequest header. When using the Accept request header, ensure that this request header has the correct value. Use the following values to specify output type.


Output Type
Accept header Value
XML
application/xml
JSON
application/json


In Java, set the Accept header in the following ways:

String url =
 "http://partnerapi.zoominfo.com/partnerapi/person/search?firstName=joe&pc=
PartnerCode&key=EncryptedKey";
HttpClient client = new HttpClient();
GetMethod get = new GetMethod(url);
get.setRequestHeader("Accept", "application/json");
client.executeMethod(get);

The resulting HTTP request should contain the following content:

GET
"http://partnerapi.zoominfo.com/partnerapi/person/search?firstName=joe&pc=
 PartnerCode&key=EncryptedKey";
Accept application/json
Host …..
Origin ….


When using both OutputType query string parameter and the HTTP Accept header together in the request, the value of OutputType will overrule the Accept header. If the request has neitherOutputType nor Accept header set, the API Server will choose XML as the default output type.

API XML Output Schemas:

The XML Schema API is the interface that allows programs and scripts to access and query information sets. This specification also defines interfaces for loading XML schema documents. The following URLs provide the locations of the published XSDs for each query.

Zoominfo’s API system has two-authentication methods. First authentication method uses Oauth (this is the preferred method of authentication), and second authentication uses MD5 Key. Note that person match existence query type does not use any authentication.

Following is a list of endpoints that are categorized based on authentication method. These are in the order of endpoints that use oauth, md5-key, and that use none.


Endpoints that use Oauth


Person Search (output)

Person Detail (output)

Person Match (Output)

Enhanced Person Match(Output)

Company Search (output)

Company Detail (output)

Company Match (output)

Usage Query (output)

 

Endpoints that use MD5


Person Search (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/PeopleQuery.xsd

Person Detail (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/PersonDetail.xsd

Person Match (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/PersonMatchResponse.xsd

Company Search (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/CompanyQuery.xsd

Company Detail (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/CompanyDetail.xsd

Company Match (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/CompanyMatchResponse.xsd

Usage Query (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/UsageQueryResponse.xsd


Endpoints that do not use any authentication


Person Match Existence (output)

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/PersonMatchExistenceResponse.xsd

http://partnerapi.zoominfo.com/partnerapistatic/xsd/V4/PersonMatchExistenceResponse.xsd


Was this article helpful?

Can’t find what you’re looking for?

Contact our award-winning customer care team.