My Profile

Under each heading on the ‘Profile’ page, you will see an ‘Add’ button for each section that allows you to submit new information for your professional profile.
If you claimed an existing profile, you may see incomplete records in these sections that can be updated by clicking ‘Edit’ to the right of each record. Please remember that anything you submit in these sections will be visible (and often searchable) on our site.

NOTE: If clicking ‘Add’ or ‘Edit’ has no effect, you may have a pop-up blocker installed on your web browser.

Edit Contact Information
To publish your email address on your profile so that others can view it, select Allow people to contact me through this email.

Add a picture
When ZoomInfo can find a picture associated with your employment history on public web documents, it will often be displayed on your profile. If you would like to add a photo to your profile or change the existing photo, click ‘Add’ or ‘Edit’ under the photo icon and browse to an image file on your computer. The file you upload must be in the JPG or GIF format and should not be over 1 MB in size. The photo will be resized to a width of 90 pixels upon upload.

Add/Edit Employment History
Indicate the chronology of your employment history by entering a Start Date and End Date for each position. These dates will not be displayed on our public website. If you are still working in a position, select No End Date in the End Date field; otherwise, your current title will be shown as a past position. By default, the position listed first on your profile will be the current position you have held the longest. If you would like a different position to be listed first on your profile, click the ‘Edit’ button next to that position and click the reads List this job first in my profile checkbox.

Add a Biography
Your ZoomInfo account gives you the ability to include a few sentences in the Biography section to describe your professional history.

If one of the online sources on your profile is fraudulent or does not refer to you please click ‘Remove’ to the right of it. Please note that if other web references are from the same site as the one being removed, then all such web references will be removed from your profile.

At the present time, your ZoomInfo account does not give you the ability to add new web references. A ZoomInfo profile serves as an objective review of web sources that mention a person's name across many different business-related websites.

NOTE: ZoomInfo has no control over the search results on other search engines like Google and Yahoo, and when a profile is updated on our site you will not see real-time results on external search engines. Many major search engines index our content from time to time, and when their software learns that a page has been updated or removed they will be likely to update the listings in their search results. However, ZoomInfo does not have control over that process.

Claim multiple profiles
Click the ‘Claim’ button to search for and consolidate multiple profiles found in the ZoomInfo database. At the present time, you cannot claim a profile that contains a different last name, such as a maiden or married name. If you are mentioned in the ZoomInfo search under more than one name, you may wish to create additional profiles for those names and mention the multiple names in the Biography section. Keep in mind that each profile must be created and verified with a unique email address.

Featured Resources

ZoomInfo's whitepapers, guides and webinars offer useful information for sales and marketing professionals – newbies and seasoned executives alike. Start exploring how ZoomInfo can help you generate more leads, prospect better and increase revenue at your organization.

API Documentation

Table of Contents

  1. Partner API Overview
  2. Using Partner APIs
  3. Output Format
  4. API Request Information
  5. Service Level Agreement
  6. Person Search
  7. Person Detail
  8. Person Match
  9. Company Search
  10. Company Detail
  11. Company Match
  12. Usage
  13. Appendix

ZoomInfo Partner API Documentation

The following documentation covers all aspects of the ZoomInfo Partner API. If you have questions, please email partnerAPI@zoominfo.com

1. Partner API Overview

ZoomInfo provides advanced search capability focused on people, companies, and their relationships. The ZoomInfo Partner API allows you to integrate ZoomInfo functionality and data into your CRM (Customer Relationship Management), MA tool (Marketing Automation), or other data system (cloud-based tools).

ZoomInfo data is extracted, analyzed, and verified to provide accurate information. To access the information, API web service calls are made via HTTP requests which provide access to information via queries. Data on people and companies can then flow into your CRM to be used in your organization.

Web Services and HTTP Requests

The ZoomInfo Partner API is a set of web services that provide access to information via HTTP requests. ZoomInfo Partner API requests, or calls, are made through properly formed URLs. The URLs are created manually or programmatically. There are several parts to the URL that need to be composed correctly in order for the request to succeed and return data. The remainder of this section provides an overview of the ZoomInfo Partner API and the types of data that it returns.

API Query Types

ZoomInfo's Partner API consists of several query types that provide search functionality and easy access to data for people and companies to help you identify and qualify prospects for your B2B marketing campaigns and sales activities. These query types are described below.

Function

Description

Person Search

Returns a list of people from ZoomInfo's data who meet the search criteria.

Person Detail

Returns detail data for a single person including name, current position, management level, past position, education history, contact information, web references, etc.

Person Match

Finds one or more people in ZoomInfo's data who are the same as, or match, the person represented by the input data.

Company Search

Returns a list of companies from ZoomInfo's data which meet the search criteria.

Company Detail

Returns detail data for a single company including company name, ticker, contact information, industries, description, key people, etc.

Company Match

Finds one or more companies in ZoomInfo's data which are the same as, or match, the company represented by the input data.

Usage Query

Provides remaining usage information andusage limits information for selected query types.

Click on the above query type name to go directly to its section in this document.

API Query Parameters

Each of the API queries in the previous table takes one or more query parameters that help identify the type of information that you are searching for. For example, when you want to perform a Person Search, you can specify an optional personTitle query parameter to narrow down your search to only those people who have a specific title. The number and type of query parameters, and whether they are required or optional, varies depending on the type of ZoomInfo Partner API query that you are using.

Search vs Match

ZoomInfo Partner API queries are named based on the type of search that they perform. Generally, it's either a search or a match.

  • Search refers to when a user specifies criteria, then gets results back.
  • Match refers to when the user already has some information, then wants to find that exact person or company in ZoomInfo's data and, if an exact match is found, get back additional information about that person or company. Match can also be used to verify if the information the user has is still valid.

So search is seeking information, while match is completing or validating information.

Authentication and Security

To provide secure access to ZoomInfo data and confidentiality for your activities, the ZoomInfo Partner API uses message authentication and encryption. We provide each partner with a Partner Password and a Partner Code (name) that is entered as part of each request to the ZoomInfo Partner API. The Partner Code and Encrypted Key (containing your Partner Password) provide a means of authenticating partners' access to the web services that make up the ZoomInfo Partner API and provide access to ZoomInfo data. All ZoomInfo Partner API requests and responses are encrypted via Transport Layer Security (TLS) to ensure partner confidentiality.

Service Level Agreement with ZoomInfo

The type of ZoomInfo Partner API queries, the frequency with which you can issue them, and the data returned by the queries is dependent upon the scope of features as defined in your Service Level Agreement (SLA).

Supported Output Formats – XML or JSON

Results can be returned in XML (Extensible Markup Language) or JSON (JavaScript Object Notation). You can obtain up to 5,000 output results per request.

2. Using Partner APIs

The ZoomInfo Partner API consists of the following web services with associated URLs that you use to access ZoomInfo data.

API

URL

Person Search

http://partnerapi.zoominfo.com/partnerapi/person/search?

Person Detail

http://partnerapi.zoominfo.com/partnerapi/person/detail?

Person Match

http://partnerapi.zoominfo.com/partnerapi/person/match?

Company Search

http://partnerapi.zoominfo.com/partnerapi/company/search?

Company Detail

http://partnerapi.zoominfo.com/partnerapi/compan/detail?

Company Match

http://partnerapi.zoominfo.com/partnerapi/compan/match?

Usage Query

http://partnerapi.zoominfo.com/partnerapi/usage/query?


The next section provides more information about the basic parts of the URL that are shared by all of the ZoomInfo Partner API queries.

API Requests and URL Construction

Since Partner API requests are made via HTTP, there are several different parts to URL construction. Each part needs to be constructed correctly in order for the search to work properly. For example, in a Company Search, you can form the URL in 3 parts. The first portion of the URL contains the partner API host name and root context followed by the query request type as shown below:

The second part of the URL contains the search parameters. For example, for a Company Search looking for ZoomInfo in Massachusetts, you would set up the next part of the URL like this:

Notice that the name of the state is spelled out in full. Two-letter state names are not supported.

The third part of the URL contains the authentication. Enter your Partner Code (or Partner Name) supplied to you by ZoomInfo as ;pc=PartnerCode. Also, you must include the encryption key which needs to be generated with parts of your search criteria, a Partner Password, and the current date. Then the key is encrypted using MD5.

Note: Substitute your Partner Code (partner name) into the URL and your Partner Password into the Key.

The next section, Security Key and Encryption, provides more information on generating encrypted keys.

Security Key and Encryption

When constructing a ZoomInfo API query, an important part of the associated URL is the security key. The key contains information specific to the ZoomInfo API request that you are making, your partner password, and the current date. The security key has the following general form:

The security key contains the following concatenated elements in order:

  • The first 2 characters of each parameter value with a yes in the Key column in the order listed in the Input Parameters Table for the given request. Note: this could also be numerals if the input parameter is a number (ex. Industry Classification number).
  • Your Partner Password
  • Today's Date

Date Structure in Keys

In structuring the Key, dates are set up in a specific order: first day, then month, then year (with no padded zeros). The date that you use is Today's Date. Be sure to use the correct order in entering the date. Here are a few example key dates.

Date

Day / Month / Year

Key Date

July 4, 2014

4 7 2014

472014

August 30, 2015

30 8 2015

3082015

November 3, 2016

3 11 2016

3112016

December 25, 2017

25 12 2017

25122017

Encrypting the Key

The entire security key must be encoded using the MD5 (Message Digest 5) encryption algorithm in UTF-8 format before issuing the query to ZoomInfo. MD5 is a simple, fast, one-way encryption algorithm, developed by RSA, which you can implement in any development language. Various MD5 encryption tools are available on the web.

The following example shows a Company Search query. The input parameters include:

  • zoominfo for companyName
  • Massachusetts for state

The query is run on the following date:

  • July 30, 2014

The key contains: the first 2 characters of the search criteria, the first 2 characters of the next search criteria, a partner password, then the date. The key before encryption would look like this

	zoMaPassword3072014

where zo is the 1st 2 characters in zoominfo and Ma is the 1st 2 characters in Massachusetts. For Password, enter your Partner Password. The date is formed as 30 7 2014 [first day, then month, then year (with no padded zeros) ].

After MD5 encryption, the key would look like this:

	e93dad4629edc678eaf80bae551b812b    

Thus, the URL would look like this

http://partnerapi.zoominfo.com/partnerapi/company/search?companyName=zoominfo&state=Massachusetts&pc=PartnerCode&key=EncryptedKey

With the above encrypted key, the URL would look like this

http://partnerapi.zoominfo.com/partnerapi/company/search?companyName=zoominfo&state=Massachusetts&pc=PartnerCode&key=e93dad4629edc678eaf80bae551b812b

Note: Since your partner password is entered into the Key (before encryption), each key is for individual use only and the above example will not work on your system until you create your own key.

The next section, Input Parameters, provides more information about which characters or digits get included in the key.

Note: Capitalization matters in regard to key generation. If you capitalize the first 2 characters of the input parameter, then you must capitalize the corresponding letter in the key (ex. zo for zoominfo & Ma for Massachusetts).

Input Parameters Used in Key Generation

Each of the Partner APIs is described in detail in their own sections in this document. Below you will find a subset of Input Parameters for the Person Search API. Notice in the table there is a heading marked Key. All the parameters of this subset are marked Yes in the Key Column to designate that they are indeed used in key generation. (Note, in the full parameter table, many parameters are marked No.)

Group

Parameter

Description

Key

Name

firstName

First name of the person being searched for

yes

middleInitial

Middle initial of the person being searched for

yes

lastName

Last name of the person being searched for

yes

Title

personTitle

Title of the person being searched for (ex. VP of Sales)

yes

TitleSeniority

Restricts searches to people in one or more of the following: Board Members, Executives, Mid Management, Non Management, C_EXECUTIVES, VP_EXECUTIVES, DIRECTOR, MANAGER. Accepts multiple values by passing a comma-separated list.

yes

TitleClassification

Restricts searches to people with a title related to the title classification specified. Accepts multiple values by passing a comma-separated list.

yes

Company ID

companyId

Searches for people who work or have worked for the specific company which has this unique ZoomInfo company ID.

yes

Company Name

companyName

Searches for people who work or have worked for a specific company.

yes

Industry / Keyword

companyDesc

Search for people whose companies contain the given description.

yes

IndustryClassification

A hierarchy of industries. See list of industry codes here. Searches for people within these industries. Accepts multiple values by passing a comma-separated list.

yes

Geography

State

Searches for people in one or more US states. Ex. Pennsylvania. Accepts multiple values by passing a comma-separated list. Note: State abbreviations are not yet supported.

yes

MetroRegion

Searches for people in one or more metro regions. Ex. Detroit, MI. Accepts multiple values by passing a comma-separated list.

yes

Country

Searches for people in one or more countries. The available countries are USA, UK, Canada, and Australia. Accepts multiple values by passing a comma-separated list.

yes

ZipCode

Restricts search to an area determined by zip code. Use this parameter in combination with RadiusMiles to increase the size of the area to search.

yes

RadiusMiles

Used in conjunction with ZipCode, designates how far in miles from zip code to include in search.

yes

Company Size

RevenueClassificationMin

Minimum revenue dollar amount of a company. Use this parameter with RevenueClassificationMax to set a range.

yes

RevenueClassificationMax

Maximum revenue dollar amount of a company. Use this parameter with RevenueClassificationMin to set a range.

yes

EmployeeSizeClassificationMin

Minimum employee size of a company. Use this parameter with EmployeeSizeClassificationMax to set a range.

yes

EmployeeSizeClassificationMax

Maximum employee size of a company. Use this parameter with EmployeeSizeClassificationMin to set a range.

yes

IsPublic

Restricts searches to people in just publicly traded or just privately held companies. Leave blank to search for people in public and private companies.

yes

CompanyRanking

Restricts searches to a company in a specific ranked list ex. Fortune 500. Accepts multiple values by passing a comma-separated list.

yes

Education

school

Searches for people who attended a specific school or university.

yes

degree

Searches for people who have received a specific type of degree (Ex. bachelors, masters, etc).

yes

Diversity

gender

Searches for people based on their gender.

yes

Source Website

companyDomainName

Restricts searches to those people who are found on a specific website.

yes

Credentials

titleCertification

Searches for people who hold a certain credential or certification (ex. Registered Nurse). This input parameter searches both current and past titles for the specified credential or certification.

yes

Date Filters

companyPastOrPresent

Designates the type of company the search criteria should be applied to: the person's present and past company, present company only, or past company only.

yes

ValidDateMonthDist

Searches for people whose profile has been updated within a certain time period.

yes

Contact Filter

ContactRequirements

Searches for people who have a certain type of contact information.

yes

Email

EmailAddress

Searches for people based on email address.

yes

The order in which the parameter appears in the table is the order in which you would use them. In key construction, you include the first 2 characters of each parameter value that you include in the search.

If the input parameter being used has only one character, then that single character can be used in the key (Ex. J for middleInitial).

Example – Person Search with Key Generation

The following example shows a Person Search query. The input parameters include:

  • Vice President for PersonTitle
  • 200714 for IndustryClassification (Search Engines & Internet Portals)
  • California for State

The query is run on the following date:

  • July 30, 2014

The key before encryption would look like this

	Vi20CaPassword3072014

where Vi is the first 2 characters in Vice President, 20 is the first 2 digits of 200714, and Ca is the first 2 characters in California. For Password, enter your Partner Password. The date is formed as 30 7 2014 [day, month, year].

After MD5 encryption, the key would look like this:

	37388ac2ee37169088980be348f50409  

Thus, the URL would look like this:

http://partnerapi.zoominfo.com/partnerapi/person/search?PersonTitle=VicePresident&IndustryClassification=200714&state=California&pc=PartnerCode&key=EncryptedKey

Using the above encrypted key, the URL would look like this:

http://partnerapi.zoominfo.com/partnerapi/person/search?PersonTitle=VicePresident&IndustryClassification=200714&state=California&pc=PartnerCode&key= 37388ac2ee37169088980be348f50409

Note: Since your partner password is entered into the Key (before encryption), each key is for individual use only and the above example will not work on your system until you create your own key.

3. 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 as firstName=name1&lastName=name2. Refer to the input parameter table for the intended query. The OutputType 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 Accept request 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 neither OutputType nor Accept header set, the API Server will choose XML as the default output type.

4. API Request Information

In this section, you will find general information on API requests including: empty XML elements, error codes, page, results per page, total results, match confidence, and XML schemas.

Empty XML Elements

Empty XML elements are almost always omitted from the output. However a few empty XML elements are output. For example, Match requests will return an empty personMatch or companyMatch XML element in the case where a particular input record results in no matches being returned.

Expected Error Responses

See the expected error responses below. For Person Match and Company Match, you will see an additional error code with each error message.

Error Response

Error Code

Causes

Invalid input parameter '<name of invalid input parameter>'

Occurs when you include an invalid parameter in a request. The error message will include the name of the invalid parameter.

Authentication failed

1002

Occurs when authentication fails due to an invalid key.

Authorization Failed

1006

Occurs due to one of the following:

·         Query Type Authorization - The partner code provided does not have permission to use the given query or match request type

·         Search Field Authorization - The partner code provided does not have permission to use one or more search parameters provided

Could not load partner '<partner code provided>'

1011

Occurs when the partner code provided is not valid.

No valid search parameters specified

1023

Occurs when you do not provide any valid search parameters in a search request. This error message occurs only for Person Detail and Company Detail queries.

No valid match parameters specified

1024

Occurs when you do not provide any valid match parameters for a match request. This error message occurs only for person match and company match requests.

Zero results returned

Occurs when you do not provide valid search parameters for a Person search or Company Search. This does not result in an actual error message, rather the resulting XML will simply contain no results.

Paging Error: Query Timeout!

Occurs when the complexity of the search query is such that we do not complete processing the query in a reasonable amount of time and therefore abort processing the query. Please try again, or simplify the search query. This error message does not occur for person match and company match requests.

The value entered for the numMatches parameter exceeds the limit on the number of match results. The limit is '<maximum number of matches per input record>'

1015

Occurs when the numMatches value which was input exceeds the maximum number of matches per input record - which is currently 10.

The number of match input records entered exceeds the limit on the number of match input records. The limit is '<maximum number of input records>'

1016

Occurs when the number of input records exceeds the maximum number of input records - which is currently 25.

You have exceeded your overall API query request limit. Please contact Zoom Information, Inc.

1013

Occurs when the query usage exceeds the overall query limit and the limit type is a hard limit.

You have exceeded your <query type> API query type request limit. Please contact Zoom Information, Inc.

1043

Occurs when the query usage exceeds the API query type query limit and the limit type is a hard limit.

Total Results

For Person Search and Company Search, the response returns a TotalResult element. The following explains how we determine this value. TotalResults is the lesser of:

  • Max API Results (5000)
  • Total number of results available
  • Results per query limit configured for the given query type based on your partner agreement

Results Per Page and Page Parameter Usage

Person Search and Company Search API requests both accept input parameters rpp and page. These parameters allow callers to page through the results of a search, having a subset of the results displayed with each response. The rpp and page parameters are intended to be used in conjunction with one another and must both be values greater than zero if specified. Your partner agreement governs the usage of these parameters and may restrict the valid values.

Page defaults to page 1 and rpp (results per page) defaults to 500. Thus, by changing only the page parameter, you can page through up to the 10th page at 500 results per page in order to get the full 5000 possible results. Additional pages are specified as follows:

&page=2, &page=3, &page=4,

For another example, if you requested rpp=25 and page=2, you would get the second page of 25 results. This would result in a response containing results 26-50 of your query.

Match Confidence

For Person Match and Company Match requests, the response returns a matchConfidence element. This value is a floating point number between 0 and 100 which represents the relative confidence in the match being returned for that input record. Generally, the more data that matched between the input record and the person or company being returned as a match, the higher the match confidence value will be.

API XML 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.

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

The XSD (XML Schema Definition) specifies how to formally describe the elements in your XML document.

5. Service Level Agreement

ZoomInfo sets limits and restrictions on the type and amount of content available. The specific limits and restrictions correspond directly with the terms outlined in the Service Level Agreement section of your contract. These limits affect the API on a per partner basis. Plans can be setup as monthly, quarterly, or yearly.

If you have questions about your Service Level Agreement and API limits please email partnerAPI@zoominfo.com

Request and Content Restrictions

Your level of usage of ZoomInfo APIs can be based on query calls or based on credits (records returned). Restrictions can apply to which API requests you are able to access. Also, each request type has restrictions on the type of content accessible to you by that query. For Person Search and Company Search, there are restrictions on which data points you are able to search by and what content you can receive back. For Person Detail, Company Detail, Person Match, and Company Match there are restrictions on the type of content you receive back on a person or company.

Overall API Call Limit

The primary limit on your account is an overall API limit that sets the restriction of how many overall API calls your account is allowed to make in a given time period. This limit applies to all query types. When the query usage exceeds the query limit and the limit type is a hard limit, the API returns the following error:

You have exceeded your overall API query request limit.
Please contact Zoom Information, Inc.

Query-Specific Limit

The next limit on your account is a query-specific limit that restricts the number of times your account is allowed to call a specific query in a given time period. (This limit applies to all query types.) When the query usage exceeds the query limit and the limit type is a hard limit, the API returns the following error:

You have exceeded your <query type> API query	type request limit. 
Please contact Zoom Information, Inc.

Search Result Query Limit

Another limit for accounts is a search result query limit. On each search query result (Person and Company), a given API call has a limit on the maximum amount of results returned. This limit does not apply to person and company match requests.

For Person Match and Company Match requests, all accounts have two additional limits:

  • Number of input records
    A person or company match GET request is considered to be one input record. Therefore, this limit will never come into play for person and company match GET requests. This limit is 1.

  • Number of match results per input record
    For each input record passed into a person or company match request, that input record has a limit on the maximum number of match results returned. This limit is 10.

6. Person Search

Person Search returns a list of people who meet the specified search criteria. The search criteria are based on the input parameters. The HTTP request for Person Search begins with the URL structure:

	http://partnerapi.zoominfo.com/partnerapi/person/search? 

Input Parameters – Person Search

When you form a Person Search query, you have different input options. Input parameter descriptions are grouped as follows:

  • Group - The grouping for search field permissions.
  • Field Name - The name of the input parameter.
  • Required - Denotes whether or not the field is required in a query.
  • Value - Valid values for the input parameter.
  • Notes - Information related to the input parameter.
  • Key - Denotes whether or not this field is used in key generation. The order in which the parameters appear in the table is the order in which you should use them in the key.

Group

Field Name

Required

Value

Notes

Key

Default

pc

required

Partner code (name) assigned to you

no

outputType

optional

xml or json

Output type of the response. Case insensitive.

no

outputFieldOptions

optional

 

Person Search has the following optional output fields:

·         localAddress

·         companyAddress

·         companyRevenue

·         companyEmployeeCount

·         companyWebsite

·         jobFunction

·         managementLevel

To return one or more of these fields, specify the above output field name(s). To return multiple output fields, separate the values with a comma. Ex: "outputFieldOptions=localAddress,companyAddress" will return localAddress and companyaddress in the output,

no

key

required

String consisting of 5 parameters concatenated together, and then encrypted with MD5. Parameters are:
1) first 2 characters of every search term
2) your partner password
3) today's day (not padded with zero)
4) today's month (not padded with zero)
5) today's year (4 digit)

no

Results Per Page

rpp

optional

Limits the results returned to the given number of results per page

no

page

optional

Provides the results for the given page, used in conjunction with rpp

no

Sort

SortBy

optional

See list of values.

Designates by which field you want to sort the results. You must provide SortBy parameters if specifying SortOrder. By default, we sort the results by relevance.

no

SortOrder

optional

asc or desc

Default value is desc. Provide SortBy if specifying SortOrder.

no

Name

firstName

optional

First name of the person being searched for

yes

middleInitial

optional

Middle initial of the person being searched for

yes

lastName

optional

Last name of the person being searched for

yes

Title

personTitle

optional

Title of the person being searched for (ex. VP of sales)

yes

TitleSeniority

optional

See list of values.

Restricts searches to people in one or more of the following: Board Members, Executives, Mid Management, Non Management, C_EXECUTIVES, VP_EXECUTIVES, DIRECTOR, MANAGER. Accepts multiple values by passing a comma-separated list.

yes

TitleClassification

optional

See list of values.

Restricts searches to people with a title related to the title classification specified. Accepts multiple values by passing a comma-separated list.

yes

Company ID

companyId

optional

Searches for people who work or have worked for the specific company which has this unique ZoomInfo company ID.

yes

Company Name

companyName

optional

Searches for people who work or have worked for a specific company.

yes

Industry/Keyword

companyDesc

optional

Search for people whose companies contain the given description.

yes

IndustryClassification

optional

See list of values.

A hierarchy of industries. See list of industry codes here. Accepts multiple values by passing a comma-separated list. Searches for people within these industries.

yes

Geography

State

optional

See list of values.

Searches for people in one or more US states. Accepts multiple values by passing a comma-separated list. You must not use State abbreviations. We will enhance the Partner API to support state abbreviations in the future.

yes

MetroRegion

optional

See list of values.

Searches for people in one or more metro regions (ex. Detroit, MI). Accepts multiple values by passing a comma-separated list.

yes

Country

optional

See list of values

Searches for people in one or more countries. The available countries are USA, UK, Canada, and Australia. Accepts multiple values by passing a comma-separated list.

yes

ZipCode

optional

Restricts search to an area determined by zip code. Use this parameter in combination with RadiusMiles to increase the size of the area to search.

yes

RadiusMiles

optional

See list of values.

Used in conjunction with ZipCode, designates how far in miles from zip code to include in search.

yes

Company Size

RevenueClassificationMin

optional

See list of values.

Minimum revenue dollar amount of a company. Use this parameter with RevenueClassificationMax to set a range.

yes

RevenueClassificationMax

optional

See list of values.

Maximum revenue dollar amount of a company. Use this parameter with RevenueClassificationMin to set a range.

yes

EmployeeSizeClassificationMin

optional

See list of values.

Minimum employee size of a company. Use this parameter with EmployeeSizeClassificationMax to set a range.

yes

EmployeeSizeClassificationMax

optional

See list of values.

Maximum employee size of a company. Use this parameter with EmployeeSizeClassificationMin to set a range.

yes

IsPublic

optional

"Public", "Private"

Restricts searches to people in just publicly traded or just privately held companies. Leave blank to search for people in public and private companies.

yes

CompanyRanking

optional

See list of values.

Restricts searches to a company in a specific ranked list Ex. Fortune 500. Accepts multiple values by passing a comma-separated list.

yes

Education

school

optional

Searches for people who attended a specific school or university.

yes

degree

optional

Searches for people who have received a specific type of degree (ex. bachelors, masters, etc).

yes

Diversity

gender

optional

"Female" ,"Male"

Searches for people based on their gender.

yes

Source Website

companyDomainName

optional

Restricts searches to those people who are found on a specific website.

yes

Credentials

titleCertification

optional

Searches for people who hold a certain credential or certification (ex. Registered Nurse). This input parameter searches both current and past titles for the specified credential or certification.

yes

Date Filters

companyPastOrPresent

optional

See list of values.

Designates the type of company the search criteria should be applied to: the person's present and past company, present company only, or past company only.

yes

ValidDateMonthDist

optional

Time period in months

Searches for people whose profile has been updated within a certain time period.

yes

Contact Filter

ContactRequirements

optional

See list of values.

Searches for people who have a certain type of contact information.

yes

Email

EmailAddress

optional

Searches for people based on email address.

yes

Example Person Search Query

The following example shows a Person Search query. The input parameters include:

  • President for personTitle
  • 33624074 for IndustryClassification (Television Stations)
  • New%20York for State

Note: We used %20 to denote where a space occurs in the state name for the example .

The Person Search query request should be structured as follows:

http://partnerapi.zoominfo.com/partnerapi/person/search?pc=PartnerCode&personTitle=President&IndustryClassification=33624074&State=New%20York&key=EncryptedKey

If the query was run on August 31, 2014, then the key would include the following combination of numbers and letters:

      Pr33NePassword3182014

After MD5 encryption, the key would be:

      a6768d549489bd734fa978c9f022e00c

With this key, the query request would be composed as follows:

http://partnerapi.zoominfo.com/partnerapi/person/search?pc=PartnerCode&personTitle=President&IndustryClassification=33624074&State=New%20York&key=a6768d549489bd734fa978c9f022e00c

The resulting Person Search output would appear in XML as follows:

<PeopleSearchRequest
    xmlns="http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/
PeopleQuery.xsd">
  <SearchParameters>
    <Parameter>
      <Name>persontitle</Name>
      <Value>President</Value>
    </Parameter>
    <Parameter>
      <Name>industryclassification</Name>
      <Value>33624074</Value>
    </Parameter>
    <Parameter>
      <Name>state</Name>
      <Value>New York</Value>
    </Parameter>
  </SearchParameters>
  <TotalResults>1037</TotalResults>
  <PeopleSearchResults>
    <PersonRecord>
      <PersonID>17868088</PersonID>
      <ZoomPersonUrl> http://www.zoominfo.com/#!search/profile/person?personId=17868088&
        targetid=profile </ZoomPersonUrl>
      <PersonDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/person/detail?query_type=
        person_detail&PersonID=17868088&pc=PartnerCode&key=EncryptedKey </PersonDetailXmlUrl>
      <LastMentioned>7/3/2014</LastMentioned>
      <IsUserPosted>False</IsUserPosted>
      <IsPast>False</IsPast>
      <ReferencesCount>78</ReferencesCount>
      <FirstName>Warner</FirstName>
      <LastName>Saunders</LastName>
      <Fax>(212) 664-4426</Fax>
      <CurrentEmployment>
        <JobTitle>Chief Newscaster</JobTitle>
        <Company>
          <CompanyID>26968099</CompanyID>
          <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=26968099&
            targetid=profile </ZoomCompanyUrl>
          <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_
            detail&CompanyID=26968099&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
          <CompanyName>NBC</CompanyName>
          <CompanyPhone>(212)
            664-4444</CompanyPhone>
        </Company>
      </CurrentEmployment>
      <Industry>Television Stations</Industry>
    </PersonRecord>
    <PersonRecord>
      <PersonID>2127155</PersonID>
      <ZoomPersonUrl> http://www.zoominfo.com/#!search/profile/person?personId=2127155&
        targetid=profile </ZoomPersonUrl>
      <PersonDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/person/detail?query_type=
        person_detail&PersonID=2127155&pc=PartnerCode&key=EncryptedKey </PersonDetailXmlUrl>
      <LastMentioned>7/3/2014</LastMentioned>
      <IsUserPosted>False</IsUserPosted>
      <IsPast>False</IsPast>
      <ReferencesCount>583</ReferencesCount>
      <ImageUrl> http://wif.org/images/repository/about/board-of-directors/
        susanne_daniels_udpate_web.jpg </ImageUrl>
      <FirstName>Susanne</FirstName>
      <LastName>Daniels</LastName>
      <Fax>(212) 354-9001</Fax>
      <CurrentEmployment>
        <JobTitle>President of Programming</JobTitle>
        <Company>
          <CompanyID>25838309</CompanyID>
          <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=25838309&
            targetid=profile </ZoomCompanyUrl>
          <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=
            company_detail&CompanyID=25838309&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
          <CompanyName>MTV</CompanyName>
          <CompanyPhone>(212)
            654-9000</CompanyPhone>
        </Company>
      </CurrentEmployment>
      <Industry>Television Stations</Industry>
    </PersonRecord>
    .... </PeopleSearchResults>
</PeopleSearchRequest>

Output Parameters – Person Search

Person Search returns a list of people in ZoomInfo's data who meet the search criteria. Output parameter descriptions are grouped as follows:

  • Group - The grouping for output field permissions. Permission groups determine the output fields present in a response for a partner.
  • Parent Name - Name of the output element
  • Child Name - Name of a child element of a parent element specified in the parent name column
  • Notes - Information related to the output field

Group

Parent Name

Child Name

Notes

Default

PersonID

Unique identifier for the person

ZoomPersonURL

URL for the person's zoominfo.com public profile

PersonDetailXmlUrl

API request URL for Person Detail. Returned output will be in XML format

LastMentioned

Date the person's profile was last updated

IsUserPosted

Designates if the profile was manually created by the person

IsPast

Designates if the most recent job title we have for a person is a past position

ReferencesCount

Number of web references the person has

ImageUrl

The URL for the person's profile image

FirstName

First name of the person

MiddleInitial

Middle initial of the person

LastName

Last name of the person

LocalAddress

The address of the person's local office

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

Street

Street for the local address.

City

City for the local address

State

State or province for the local address

Zip

Postal code for the local address

CountryCode

Country of the local address

CurrentEmployment

Current company the person is employed by. CurrentEmployment contains child elements.

JobTitle

Person's title at their current place of employment

JobFunction

Person's job function at their current place of employment.

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

ManagementLevel

Person's management level at their current place of employment

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

Company

Contains child elements with information about the person's current company

CompanyID

Unique identifier used by ZoomInfo for company

ZoomCompanyUrl

URL for the company's zoominfo.com public profile

CompanyDetailXmlUrl

API request URL for Company Detail. Returned output will be in XML format

CompanyName

Name of the company

CompanyPhone

Phone number of the company headquarters.

CompanyAddress

Address of the person's current company headquarters

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this

Street

Street for company

City

City for company

State

State or Province of the company

Zip

Postal Code

Country

Country of the Company

CompanyWebsite

The URL for the company. Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field.

CompanyRevenue

Annual gross revenue for the company. Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

CompanyEmployeeCount

Employee head count for the company. Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

Industry

Industry

Industry the person currently works in. A person can have multiple industries. Industry tags are based on the current employment company.

Contact Info

Email

You will see ###### if the permission to this output field is not granted

Person's email address in example@example.com format

Phone

You will see ###### if the permission to this output field is not granted

The person's direct phone number, if available.

Fax

You will see ###### if the permission to this output field is not granted

The fax number for the person's current company

7. Person Detail

Person Detail returns a wide array of person-specific information for each unique identifier passed. Person summary data includes name, current position, management level, past position, education history, contact information, web references, etc. Your level of access rights will determine the amount of data returned. The HTTP request for Person Detail begins with the URL structure:

  http://partnerapi.zoominfo.com/partnerapi/person/detail?  

Input Parameters – Person Detail

Person Detail input parameter descriptions are grouped as follows:

  • Group - The grouping for search field permissions.
  • Field Name - Name of input parameter.
  • Required - Denotes whether or not a query requires the field.
  • Value - Valid values for the input parameter.
  • Notes - Information related to the input parameter.
  • Key - Denotes whether or not this field is used in key generation. The order in which the parameters appear in the table is the order in which you should use them in the key.

Group

Field Name

Required

Value

Notes

Key

Default

pc

required

 

Partner code (name) assigned to you

no

outputType

optional

xml or json

The output format type of the response. Case insensitive.

no

outputFieldOptions

optional

 

Person Detail Query has the following optional output fields:

·         jobFunction

·         managementLevel

To return one or more of these fields, specify the above output field name(s). To return multiple optional output fields, separate the values with a comma. For example, "outputFieldOptions=jobFunction,managementLevel" will return jobFunction and managementLevel in the output.

no

key

required

String consisting of 5 parameters concatenated together, and then encrypted with MD5. Parameters are:
1) First two characters of PersonID (query dependent) and first two characters of EmailAddress (query dependent)
2) your partner password
3) today's day (not padded with zero)
4) today's month (not padded with zero)
5) today's year (4 digit)

no

PersonID or EmailAddress

PersonID

optional

Unique identifier for a person in the ZoomInfo database

yes

EmailAddress

optional

Person's email address in example@example.com format. If both PersonID and EmailAddress are provided, then EmailAddress is ignored.

yes

Example Person Detail Query

The following example shows a Person Detail query. The input parameter includes:

  • 457877 for PersonID

The Person Detail query request should be structured as follows:

http://partnerapi.zoominfo.com/partnerapi/person/detail?pc=PartnerCode&PersonID=457877&key=EncryptedKey

The Person Detail XML output would appear as follows:

<PersonDetailRequest
    xmlns="http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/PersonDetail.xsd">
  <PersonID>457877</PersonID>
  <ZoomPersonUrl> http://www.zoominfo.com/#!search/profile/person?personId=457877&
    targetid=profile </ZoomPersonUrl>
  <LastUpdatedDate>2014-06-16</LastUpdatedDate>
  <IsUserPosted>true</IsUserPosted>
  <ImageUrl> http://www.zoominfo.com/business/images/stories/managementteam/yonatan-stern-photo.jpg </ImageUrl>
  <FirstName>Jonathan</FirstName>
  <LastName>Stern</LastName>
  <Email>example@example.com</Email>
  <CompanyPhone>(555)
    555-7500</CompanyPhone>
  <CurrentEmployment>
    <JobTitle>Founder and Chief Executive Officer</JobTitle>
    <Company> <CompanyID>344589814</CompanyID> <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=344589814&targetid=profile </ZoomCompanyUrl> <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=344589814&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl> <CompanyName>Zoom Information, Inc.</CompanyName> <Phone>(555) 555-7500</Phone> <Fax>(555) 555-7000</Fax> <Website>www.zoominfo.com</Website> <CompanyAddress>   <Street>307 Waverley Oaks Rd.</Street>   <City>Waltham</City>   <State>Massachusetts</State>   <Zip>02452</Zip>   <CountryCode>United States</CountryCode> </CompanyAddress>
    </Company>
  </CurrentEmployment>
  <PastEmployment>
    <JobTitle>Founder and Chief Executive Officer</JobTitle>
    <Company> <CompanyID>6750984</CompanyID> <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=6750984&targetid=profile </ZoomCompanyUrl> <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=   company_detail&CompanyID=6750984&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl> <CompanyName>CardScan Inc</CompanyName> <Website>www.cardscan.com</Website> <CompanyAddress>   <City>Cambridge</City>   <State>Massachusetts</State>   <CountryCode>United States</CountryCode> </CompanyAddress>
    </Company>
  </PastEmployment>
  ...
  <Industry>Software & Technical
    Consulting</Industry>
  <Industry>Search Engines & Internet
    Portals</Industry>
  <Industry>Customer Relationship Management (CRM)
    Software</Industry>
  <WebReference>
    <Title>Leadership | ZoomInfo</Title>
    <Url>http://www.zoominfo.com/business/about/leadership</Url>
    <Description> Jonathan Stern Yonatan Stern Founder, CEO & Chief Scientist Yonatan Stern Founder, CEO & Chief Scientist, ZoomInfo </Description>
    <Date>2014-06-04</Date>
  </WebReference>
  <WebReference>
    <Url> http://www.kipling.thefreelibrary.com/SALES+LEAD+MANAGEMENT+ASSOCIATION+HONORS+ZOOMINFO+VP+OF+MARKETING.-a0363482177 </Url>
    <Description> "Nir and her team's contributions have significantly impacted ZoomInfo's revenue growth and bottom line," said Yonatan Stern, ZoomInfo's founder, CEO(1) (Chief Executive Officer) The highest individual in command of an organization. </Description>
    <Date>2014-04-01</Date>
  </WebReference>
  <WebReference>
    <Title>The Bizo Executive Team |
    Bizo</Title>
    <Url>http://www.bizo.com/about/team</Url>
    <Description> Yonatan Stern, Founder and Director Yonatan co-founded Bizo and led the charge to spin it out of ZoomInfo to create his fourth company  in the last 20 years. Yonatan is currently the founder, CEO and Chief  Scientist of ZoomInfo and is ... </Description>
    <Date>2013-12-10</Date>
  </WebReference>
  <WebReference>
    <Title>Yonatan Stern | ZoomInfo</Title>
    <Url> http://www.zoominfo.com/business/about/leadership/yonatan-stern </Url>
    <Description> Yonatan Stern Founder, Chief Executive Officer & Chief Scientist Yonatan Stern founded ZoomInfo (formerly Eliyon Technologies Corporation) in 2000 and is its chief executive officer and chief scientist. For more than 30 years, Stern has been active in cognitive science research, developing useful products based on  algorithms which track the way people reason... </Description>
    <Date>2013-05-08</Date>
  </WebReference>
  <WebReference>
    <Title>Our Company | ZoomInfo</Title>
    <Url> http://www.zoominfo.com/business/about/our-company?utm_source=zoominfo.com&utm_medium=navigation&utm_content=our-company&utm_campaign=navigation_links </Url>
    <Description>Yonatan Stern</Description>
    <Date>2014-06-04</Date>
  </WebReference>
  ...
  <SummaryStatistics>
    <WebReferences>587</WebReferences>
  </SummaryStatistics>
</PersonDetailRequest>

Output Parameters – Person Detail

Person Detail output parameter descriptions are grouped as follows:

  • Group - Grouping for output field permissions. The permission groups configured for a partner determine the output fields present in a response.
  • Parent Name - Name of output element.
  • Child Name - Name of a child element of a parent element specified in the parent name column.
  • Notes - Information related to the output field.

Group

Parent Name

Child Name

Notes

Default

PersonID

Unique identifier for the person

ZoomPersonURL

Link to person's ZoomInfo.com public profile

LastUpdatedDate

Date of the last time the person's profile was updated

IsUserPosted

Designates if a profile was manually built by the person. true = manually created, false = crawled by ZoomInfo

ImageUrl

The URL to the person's profile image

Name

FirstName

First name of the person

MiddleInitial

Middle Initial of the person

LastName

Last name of the person

Email

Email

Email for the person in example@example.com format

Phone Numbers

DirectPhone

The person's direct phone number, if available

CompanyPhone

Main phone number for the person's current employment company

Current Company

CurrentEmployment

Current company the person is employed with. CurrentEmployment contains child elements.

JobTitle

Person's title at their current place of employment

JobFunction

Person's job function at their current place of employment

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

ManagementLevel

Person's management level at their current place of employment

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

FromDate

Start date of the person's current employment.

Company

Contains the child elements with information about the person's current company of employment

CompanyID

The unique identifier used by ZoomInfo for companies

ZoomCompanyUrl

Link to the company's ZoomInfo.com public profile

CompanyDetailXmlUrl

API request URL for Company Detail. Returned output will be in XML format

CompanyName

Name of the company

Phone

Primary phone number of the company

Fax

Fax number of the company

Website

The URL to the company website in http://www.example.com format

CompanyAddress

Contains child elements with the company's address

Street

Street of the company's primary address

City

City of the company's primary address

State

State of the company's primary address

Zip

Zip code of the primary address

Country Code

Country code of the primary address

Employment History

PastEmployment

Companies that have employed the person in the past. Multiple companies for employment history are allowed.

JobTitle

The person's title at a past place of employment

FromDate

Start date of the person's past employment

ToDate

End date of the person's past employment

Company

Contains the child elements with information about the person's past company of employment

CompanyID

Unique identifier used by ZoomInfo for the company

ZoomCompanyUrl

The URL to the company profile on zoominfo.com public site

CompanyDetailXmlUrl

API request URL for Company Detail. Returned output will be in XML format

CompanyName

Name of the company

Phone

Primary phone number of the company

Website

The URL to the company website in http://www.example.com format

CompanyAddress

Contains child elements with the company's address

Street

Street of the company's primary address

City

City of the company's primary address

State

State of the company's primary address

Zip

Zip code of the company's primary address

CountryCode

Country code of the company's primary address.

Education

Education

Education information for the person. Multiple educations are allowed for a person.

School

Name of the school where the person received a degree

GraduationDate

Year the person received a degree from the school

EducationDegree

Contains child elements describing the type of degree the person received from the school. A person can have more than one EducationDegree from the same school.

Degree

Type of degree the person received (BA, MBA, etc)

AreaOfStudy

Area of study (a person's major or minor) ex: Biology, Business Administration

Industry

Industry

Industry the person currently works in. A person can have multiple industries. Industry tags are based on the current employment company.

Board Memberships

Affiliation

A part time position that somebody holds. Usually affiliated with associations or board memberships. Affiliation contains child elements

JobTitle

Title of person's affiliation. Common values: Board Member, Treasurer

JobFunction

Job function of person's affiliation

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

ManagementLevel

Management level of person's affiliation

Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

FromDate

Start date of the person's affiliation

ToDate

End date of the person's affiliation

Company

Contains the child elements with information about the person's company of employment

CompanyID

The unique identifier used by ZoomInfo for the company

ZoomCompanyUrl

The URL to the company profile on zoominfo.com public site

CompanyDetailXmlUrl

API request URL for Company Detail. Returned output will be in XML format

CompanyName

Name of the company

Phone

Primary phone number of the company

Website

The URL to the company website in http://www.example.com format

CompanyAddress

Contains child elements describing the company's primary address

Street

Street of the company's primary address

City

City of the company's primary address

State

State of the company's primary address

Zip

Zip code of the company's primary address

Country code

Country code of the company's primary address

Certifications

Certifications

Describes an accreditation received by an organization. ( CPA, Registered Nurse, etc) Certifications contains 3 child elements

CertificationName

Name or type of certification the person has received

OrganizationName

Certifying organization

YearReceived

Year the person received the certification

Biography

Biography

A person entered summary about themselves. Only available for summaries that are manually created.

Web References

WebReference

Source document where the information was extracted. WebReference contains three child elements

Title

The title of the web source

URL

The URL to the web reference

Description

Text from the web reference where ZoomInfo crawlers found information about the company or person

Date

Date that we found the web reference

Statistics

SummaryStatistics

An overview of statistics gathered on a person's public zoominfo.com profile. SummaryStatistics contains a child element.

WebReferences

Number of web references found on a person

8. Person Match

A Person Match request returns match results of people based on criteria of various match inputs. Your partner agreement restricts the available returned match output. The HTTP request for Person Match begins with the URL structure:

  http://partnerapi.zoominfo.com/partnerapi/person/match?

Input Parameters – Person Match

The table below shows input parameters that can be used in Person Match queries. Parameter descriptions are grouped as follows:

  • Group - Grouping for match field permissions.
  • Field Name - Name of input parameter.
  • Required - Denotes whether or not the field is required in a match request.
  • Value - Valid values for this input parameter.
  • Notes - Information related to the input parameter.
  • Key - Denotes whether or not the key generation uses the field. The order in which the parameters appear in the table is the order in which you should use them in the key. For match requests, the key for each input record passed into the request must have one set of parameter values. Use each set of parameter values in the key in the same order as their respective input records.

Group

Field Name

Required

Value

Notes

Key

Request-level Default

pc

required

Partner code (or partner name) assigned to you

no

key

required

A string consisting of 5 parameters concatenated together, then encrypted with MD5. Parameters are:
1) first 2 characters of every match term in each input record
2) your partner password
3) today's day (not padded with zero)
4) today's month (not padded with zero)
5) today's year (4 digit)

no

numMatches

optional

number from 1 to 10

Limits the match results returned to the given number of match results per input record

no

echoInput

optional

true or false

Default value is false. If you set it to be false, the XML output displays only the unique Id for each input record. Alternatively, the XML output displays the unique Id and all other input parameters for each input record

no

outputFieldOptions

optional

 

Person Match Query has the following optional output fields:

·         localAddress

·         companyAddress

·         companyRevenue

·         companyEmployeeCount

·         jobFunction

·         managementLevel

To return one or more of these fields, specify the above output field name(s). To return multiple optional output fields, separate the values with a comma. For example, "outputFieldOptions=localAddress,companyAddress" will return localAddress and companyaddress in the XML output,

no

matchCompany

optional

true or false

Enables Company Match when Person Match could not find any match. Either a companyId or companyName needs to be provided. Authorization to the Company Match API is required.

no

Input Record-level Default

uniqueInputId

optional

Unique string you use to identify a particular match request input record within a match request

no

personId

optional

Unique ZoomInfo identifier of the person to be matched by a particular input record

yes

firstName

optional

First name of person to be matched by a particular input record

yes

lastName

optional

Last name of the person to be matched by a particular input record

yes

emailAddress

optional

Email address of the person to be matched by a particular input record

yes

companyId

optional

Unique ZoomInfo identifier of the company that the person to be matched by a particular input record works or has worked

yes

companyName

optional

Name of the company for which the person to be matched by a particular input record works or has worked

yes

jobTitle

optional

Current job title of the person to be matched by a particular input record

yes

Example Person Match Request

The following example shows a Person Match query. The input parameters include:

  • true for echoInput
  • jon for firstName
  • smith for lastName
  • jsmith@leonardinsurance.com for emailAddress

  • leonard for companyName
  • The Person Match query request can be structured like this:

    http://partnerapi.zoominfo.com/partnerapi/match/person?pc=PartnerCode&firstName=jon&lastName=smith&emailAddress=jsmith@leonardinsurance.com&companyName=leonard&echoInput=true&key=EncryptedKey

    <personMatchResponse xmlns="http://partnerapi.zoominfo.com/partnerapistatic/
    xsd/V1/PersonMatchResponse.xsd">
      <inputParameters>
        <parameter>
          <name>echoInput</name>
          <value>true</value>
        </parameter>
      </inputParameters>
      <matchResults>
        <personMatchResults>
          <personMatchResult>
            <matchPersonInput>
              <uniqueInputId>Zoom-1</uniqueInputId>
              <firstName>jon</firstName>
              <lastName>smith</lastName>
              <emailAddress>jsmith@leonardinsurance.com</emailAddress>
              <companyName>leonard</companyName>
            </matchPersonInput>
            <personMatches>
              <personMatch>
                <matchConfidence>90</matchConfidence>
                <personId>-108503</personId>
                <zoomPersonUrl>http://www.staging.zoominfo.com/#!search/profile/person?personId=-108503&targetid=profile</zoomPersonUrl>
                <personDetailXmlUrl>http://api.zoominfo.staging.com/partnerapi/xmloutput.aspx
                  ?query_type=person_detail&PersonID=-
                  108503&pc=PartnerCode&key=EncryptedKey</personDetailXmlUrl>
                <lastMentioned>3/21/2013</lastMentioned>
                <isUserPosted>True</isUserPosted>
                <isPast>False</isPast>
                <referencesCount>51</referencesCount>
                <imageUrl>http://www.aogexpo.com.au/ckfinder/userfiles/images/speakers
                  /Jonathan%20Smith%20photo.jpg</imageUrl>
                <firstName>Jon</firstName>
                <lastName>Smith</lastName>
                <email>jsmith@leonardinsurance.com</email>
                <phone>(330) 266-1904</phone>
                <fax>(330) 498-9946</fax>
                <currentEmployment>
                  <jobTitle>Vice President</jobTitle>
                  <company>
                    <companyId>22462584</companyId>
                    <zoomCompanyUrl>http://www.staging.zoominfo.com/#!search/profile/company?companyId=22462584&targetid=profile</zoomCompanyUrl>
                    <companyDetailXmlUrl>http://api.zoominfo.staging.com/partnerapi/xmloutput.aspx
                      ?query_type=company_detail&CompanyID=22462584&pc=PartnerCode&
                      key=EncryptedKey</companyDetailXmlUrl>
                    <companyName>Leonard Insurance Services Agency Inc</companyName>
                    <companyPhone>(330) 266-1974</companyPhone>
                  </company>
                </currentEmployment>
                <industry>Insurance</industry>
              </personMatch>
            </personMatches>
          </personMatchResult>
        </personMatchResults>
      </matchResults>
    </personMatchResponse>

    Output Parameters – Person Match

    The table below shows output parameters that can be used in Person Match queries. These parameters are grouped in the following categories:

    • Group - The grouping for output field permissions. The permission groups configured for a partner determine the output fields present in a response.
    • Parent Name - Name of the output element
    • Child Name - Name of a child element of a parent element specified in the parent name column
    • Notes - Information related to the output field

    Group

    Parent Name

    Child Name

    Notes

    Default

    PersonID

    Unique identifier for the person

    ZoomPersonURL

    URL for the person's zoominfo.com public profile

    PersonDetailXmlUrl

    API request URL for Person Detail. Returned output will be in XML format

    LastMentioned

    Date the person's profile was last updated

    IsUserPosted

    Designates if the person created the profile manually

    IsPast

    Designates if the most recent job title for a person is a past position

    ReferencesCount

    Number of web references the person has

    ImageUrl

    URL for the person's profile image

    FirstName

    First name of the person

    MiddleInitial

    Middle initial of the person

    LastName

    Last name of the person

    LocalAddress

    Address of the person's local office

    Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

    Street

    Street for the local address.

    City

    City for the local address

    State

    State or province for the local address

    Zip

    Postal code for the local address

    CountryCode

    Country for the local address

    CurrentEmployment

    JobTitle

    Current company that employs the person. CurrentEmployment contains the following child elements.

    Person's title at current place of employment

    JobFunction

    Person's job function at their current place of employment

    Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

    ManagementLevel

    The person's management level at their current place of employment

    Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

    Company

    Contains the following child elements with information about the person's current company

    CompanyID

    Unique identifier used by ZoomInfo for company

    ZoomCompanyUrl

    URL for the company's zoominfo.com public profile

    CompanyDetailXmlUrl

    API request URL for Company Detail. Returned output will be in XML format

    CompanyName

    Name of the company

    CompanyPhone

    Phone number of the company headquarters.

    CompanyAddress

    Address for the person's current company headquarters.

    Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

    Street

    Street for the company address

    City

    City for the company address

    State

    State or province for the company address

    Zip

    Postal code for the company address

    CountryCode

    Country for the company address

    CompanyRevenue

    Annual gross revenue for the company. Optional output field: it won't be shown unless the 'outputFieldOptions' parameter contains this output

    CompanyEmployeeCount

    Employee head count for the company. Optional: It won't be shown unless the 'outputFieldOptions' parameter contains this output field

    Industry

    Industry

    Industry the person currently works in. A person can have multiple industries. Industry tags are based on the current employment company.

    Contact Info

    Email

     

    Person's email address in example@example.com format

    Phone

     

    Best available phone number for the person

    Fax

     

    Fax number for the person's current company

    Person Match – Tips

    ZoomInfo utilizes Approximate String Matching (also called, fuzzy matching) when comparing names. For example, for Person Match, the input of "Mary Beth" may match Mary Ann, Maryann, Mary Jane, Mary Lynn, or Marianne. Likewise, Anne-Marie may return a match to AnneMarie.

    9. Company Search

    The company search query provides access to full searching capability on company data. The result of the query shows a list of companies and information corresponding to the input criteria. Access rights for partner accounts are determined by your Service Level Agreement (SLA). The HTTP request for Company Search begins with the URL structure:

      http://partnerapi.zoominfo.com/partnerapi/company/search?

    Input Parameters – Company Search

    The table below shows input parameters that can be used in Company Search queries. Parameter descriptions are grouped as follows:

    • Group - The grouping for search field permissions
    • Field Name - Name of the input parameter
    • Required - Denotes whether or not a query request requires the field
    • Value - Valid values for this input parameter
    • Notes - Information related to the input parameter
    • Key - Denotes whether or not the key generation uses the field. The order in which the parameters appear in the table is the order in which you should use them in the key.

    Group

    Field Name

    Required

    Value

    Notes

    Key

    Default

    pc

    required

    Partner code (name) assigned to you

    no

    outputType

    optional

    xml or json

    The format type of the response output. Case insensitive.

    no

    key

    required

    String consisting of 5 parameters concatenated together, and then encrypted with MD5. Parameters are:
    1) first 2 characters of every search term in sequential order, based on the order presented in the input parameters table for each query
    2) your partner password
    3) today's day (not padded with zero)
    4) today's month (not padded with zero)
    5) today's year (4 digit)

    no

    outputFieldOptions

    optional

    Company Search Query has the following optional output fields:

    • companyPhone
    • companyFax

    To return one or more of these fields, specify the above output field name(s). To return multiple optional output fields, separate the values with a comma. For example, "outputFieldOptions=companyPhone,companyFax" will return companyPhone and companyFax in the XML output

    no

    Results Per Page

    rpp

    optional

    Limits the results returned to the given number of results per page

    no

    page

    optional

    Provides the results for the given page, used in conjunction with rpp

    no

    Sort

    SortBy

    optional

    See list of values.

    Designates which field is used to sort the results. SortBy is required if SortOrder is specified. When the SortBy is not specified and the IndustryClassification is specified, the returned records are sorted by IndustryClassification in decreasing industry relevance.

    no

    SortOrder

    optional

    asc or desc

    Default value is desc. SortBy is required if SortOrder is specified.

    no

    Company Name

    companyName

    optional

    The name of the company being searched for. Will also accept a stock ticker or website domain as input.

    yes

    Industry / Keyword

    companyDesc

    optional

    Search for people whose companies match the given description.

    yes

    IndustryClassification

    optional

    See list of values.

    A hierarchy of industries. See list of industry codes here. Accepts multiple values by passing a comma-separated list.

    yes

    Company Size

    RevenueClassificationMin

    optional

    See list of values.

    Minimum revenue dollar amount of a company. Use this parameter with RevenueClassificationMax to set a range.

    yes

    RevenueClassificationMax

    optional

    See list of values.

    Maximum revenue dollar amount of a company. Use this parameter with RevenueClassificationMin to set a range.

    yes

    EmployeeSizeClassificationMin

    optional

    See list of values.

    Minimum employee size of a company. Use this parameter with EmployeeSizeClassificationMax to set a range.

    yes

    EmployeeSizeClassificationMax

    optional

    See list of values.

    Maximum employee size of a company. Use this parameter with EmployeeSizeClassificationMin to set a range.

    yes

    IsPublic

    optional

    "Public", "Private"

    Restricts searches to just publicly traded or privately held companies. Leave blank to search for public and private companies.

    yes

    CompanyRanking

    optional

    See list of values.

    Restricts searches to a specific company ranked list Ex. Fortune 500. Accepts multiple values by passing a comma-separated list.

    yes

    Geography

    State

    optional

    See list of values.

    Restricts searches to one or more US states. Accepts multiple values by passing a comma-separated list. You must not use state abbreviations. We will enhance the new Partner API to support state abbreviations in the near future.

    yes

    MetroRegion

    optional

    See list of values.

    Restricts searches to one or more metro regions. Accepts multiple values by passing a comma-separated list.

    yes

    Country

    optional

    See list of values.

    Restricts to one or more countries. The only available countries are USA, UK, Canada, and Australia. Accepts multiple values by passing a comma-separated list.

    yes

    ZipCode

    optional

    Restricts search to an area determined by zip code. Use this parameter in combination with RadiusMiles to increase the size of the area to search.

    yes

    RadiusMiles

    optional

    See list of values.

    Used in conjunction with ZipCode, designates how far in miles from zip code to include in search.

    yes

    Example Company Search Query

    The following example shows a Company Search query. The input parameters include:

    • 5642 for IndustryClassification (Software Companies)
    • Florida for State

    The Company Search query request should be structured as follows:

    http://partnerapi.zoominfo.com/partnerapi/company/search?pc=PartnerCode&IndustryClassification=5642&State=Florida&key=EncryptedKey

    Note: To find a list of Industry Classification numbers, go to List of Values.

    The Company Search XML output would appear as follows:

    <CompanySearchRequest xmlns="http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/CompanyQuery.xsd">
      <SearchParameters>
        <Parameter>
          <Name>industryclassification</Name>
          <Value>5642</Value>
        </Parameter>
        <Parameter>
          <Name>state</Name>
          <Value>Florida</Value>
        </Parameter>
      </SearchParameters>
      <TotalResults>5000</TotalResults>
      <CompanySearchResults>
        <CompanyRecord>
          <CompanyID>61493009</CompanyID>
          <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=61493009&targetid=profile </ZoomCompanyUrl>
          <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=61493009&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
          <CompanyName>Citrix Systems Inc</CompanyName>
          <CompanyTicker>NASDAQ: CTXS</CompanyTicker>
          <Website>www.citrix.com</Website>
          <CompanyAddress>
            <Street>851 West Cypress Creek Road</Street>
            <City>Fort Lauderdale</City>
            <State>Florida</State>
            <Zip>33309</Zip>
            <CountryCode>United States</CountryCode>
          </CompanyAddress>
          <CompanyDescription> Citrix Systems, Inc. designs, develops and market technology solutions that allow applications to be delivered, supported, and shared on-demand with high performance, enhanced security, and improved total cost of ownership (TCO). The Company markets and licenses its products through multiple channels, such as value-added resellers (VARs), channel distributors, system integrators (Sis), independent software vendors (ISVs), its Websites and original equipment manufacturers (OEMs). The Company designs, develops, markets, sells and supports multiple products in an IT market category called Application Delivery Infrastructure. Its product family brand for all its infrastructure solutions is the Citrix Delivery Center. In October 2008, it acquired all of the issued and outstanding securities of Vapps, Inc. (Vapps).
            (Source: 10-K) </CompanyDescription>
          <Revenue>$1.6 Billion</Revenue>
          <Employees>4816</Employees>
          <Industry>Software Development & Design</Industry>
          <Industry>Software</Industry>
          <Industry>Consumer Electronics</Industry>
          <Industry>Consumer Goods</Industry>
          <Industry>Telecommunication Equipment</Industry>
          <Industry>Manufacturing</Industry>
          <Industry>Engineering Software</Industry>
          <Industry>Content & Collaboration Software</Industry>
        </CompanyRecord>
        <CompanyRecord>
          <CompanyID>39354715</CompanyID>
          <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=39354715&targetid=profile </ZoomCompanyUrl>
          <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=39354715&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
          <CompanyName>Ultimate Software incorporated</CompanyName>
          <CompanyTicker>NASDAQ: ULTI</CompanyTicker>
          <Website>www.ultimatesoftware.com</Website>
          <CompanyAddress>
            <Street>2000 Ultimate Way</Street>
            <City>Weston</City>
            <State>Florida</State>
            <Zip>33326</Zip>
            <CountryCode>United States</CountryCode>
          </CompanyAddress>
          <CompanyDescription> The Ultimate Software Group, Inc. (Ultimate Software) designs, markets, implements and supports human resources (HRs), payroll and talent management solutions in the United States and Canada. The Company's UltiPro Software (UltiPro) is a Internet-based solution designed to deliver the functionality businesses need to manage the complete employment life cycle from recruitment to retirement. The solution includes feature-sets for talent acquisition and onboarding, HR management and compliance, benefits management and online enrollment, payroll, performance management, salary planning and budgeting, reporting and analytical decision-making tools, time and attendance, and a self-service Web portal for executives, managers, administrators and employees. (Source: 10-K) </CompanyDescription>
          <Revenue>$269.2 Million</Revenue>
          <Employees>1328</Employees>
          <Industry>Software Development & Design</Industry>
          <Industry>Software</Industry>
          <Industry>Engineering Software</Industry>
          <Industry>Financial, Legal & HR Software</Industry>
        </CompanyRecord>
        <CompanyRecord>
          <CompanyID>66453522</CompanyID>
          <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=66453522&targetid=profile </ZoomCompanyUrl>
          <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=66453522&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
          <CompanyName>Web Internet LLC</CompanyName>
          <CompanyTicker>NASDAQ: WWWW</CompanyTicker>
          <Website>www.web.com</Website>
          <CompanyAddress>
            <Street>12808 Gran Bay Parkway West</Street>
            <City>Jacksonville</City>
            <State>Florida</State>
            <Zip>32258</Zip>
            <CountryCode>United States</CountryCode>
          </CompanyAddress>
          <CompanyDescription> Web.com, Inc., formerly Website Pros, Inc. is a provider of do-it-for-me and do-it-yourself Website building tools, online marketing, lead generation and technology solutions that enable small and medium-sized businesses to build and maintain an online presence. The Company offers a range of online services, including online marketing and advertising, local search, search engine marketing, search engine optimization, lead generation, home contractor specific leads, Website design and publishing, logo and brand development and eCommerce solutions, meeting the needs of small businesses anywhere along their lifecycle. On June 18, 2008, the Company acquired certain assets from LogoYes.com and Design Logic, Inc (collectively LogoYes). In April 2009, the Company acquired Solid Cactus, an eCommerce site builder and solutions provider. </CompanyDescription>
          <Revenue>$199.2 Million</Revenue>
          <Employees>1800</Employees>
          <Industry>Software Development & Design</Industry>
          <Industry>Software</Industry>
          <Industry>Business Services</Industry>
          <Industry>Search Engines & Internet Portals</Industry>
          <Industry>Media & Internet</Industry>
          <Industry>Content & Collaboration Software</Industry>
        </CompanyRecord>
        ... </CompanySearchResults>
    </CompanySearchRequest>

    Output Parameters – Company Search

    The table below shows output parameters that can be used in Company Search queries. Parameter descriptions are grouped as follows:

    • Group - The grouping for output field permissions. The permission groups configured for a partner determine the output fields present in a response.
    • Parent Name - The name of the output element
    • Child Name - The name of a child element of a parent element specified in the parent name column
    • Notes - Information related to the output field

    Group

    Parent Name

    Child Name

    Notes

    Default

    CompanyID

    Unique identifier used by ZoomInfo for companies

    ZoomCompanyUrl

    The URL to the company profile on zoominfo.com public site

    CompanyDetailXmlUrl

    API request URL for Company Detail. Returned output will be in XML format

    CompanyName

    Full name of the company

    CompanyTicker

    The company's public stock exchange ticker

    CompanyPhone

    Phone number for the company. Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

    CompanyFax

    Fax number for the company. Optional: This output field won't be shown unless the 'outputFieldOptions' parameter contains this output field

    Website

    The web domain for the company in http://www.example.com format

    CompanyAddress

    Contains 5 child elements describing the company's primary address

    Street

    Street address for the company's primary address

    City

    City for the company's primary address

    State

    State for the company's primary address

    Zip

    Zip code of the company's primary address

    CountryCode

    Country code of the company's primary address

    CompanyDescription

    A short paragraph describing the main purpose of the company

    Industry

     

    An industry grouping for the company. A company can have multiple industries.

    Revenue and Employees

    Revenue

    Approximate yearly revenue for the company

    Employees

    Approximate number of people employed by the company

    10. Company Detail

    The Company Detail query returns a wide array of company specific information for each company unique identifier passed. The access rights set for partner account limit the data returned. The HTTP request for Company Detail begins with the URL structure:

      http://partnerapi.zoominfo.com/partnerapi/company/detail?

    Input Parameters – Company Detail

    The table below shows input parameters that can be used in Company Detail queries. Parameter descriptions are grouped as follows:

    • Group - The grouping for search field permissions
    • Field Name - Name of the input parameter
    • Required - Denotes whether or not a query request requires the field
    • Value - Valid values for this input parameter
    • Notes - Information related to the input parameter
    • Key - Denotes whether or not the key generation uses the field. The order in which the parameters appear in the table is the order in which you should use them in the key.

    Group

    Field Name

    Required

    Value

    Notes

    Key

    Default

    pc

    required

    Partner code (name) assigned to you

    no

    key

    required

     

    String consisting of 5 parameters concatenated together, and then encrypted with MD5. Parameters are:
    1) First two characters of CompanyID (query dependent) and first two characters of CompanyDomain (query dependent)
    2) your partner password
    3) today's day (not padded with zero)
    4) today's month (not padded with zero)
    5) today's year (4 digit)

    no

    outputType

    optional

    xml or json

    The format type of the response content. Case insensitive.

    no

    includeKeyPerson

    optional

    true or false

    Default value is false. When set to true, this optional parameter adds the KeyPerson element to the Company Detail output, but only if you have permission to the KeyPerson output field. Be aware that adding the KeyPerson element to the Company Detail output will result in slower performance for that Company Detail query. (See KeyPerson below in the Output Parameters.)

    no

    Company ID or Company Domain

    CompanyID

    cid or domain

    The company's ZoomInfo ID

    yes

    CompanyDomain

    cid or domain

    Company's website domain address. If you provided the CompanyDomain along with CompanyID, then we would ignore CompanyDomain.

    yes

    Example Company Detail Query

    The example below shows a Company Detail request with the following input parameters:

    • www.ibm.com for CompanyDomain

    Here is the structure of the Company Detail query:

    http://partnerapi.zoominfo.com/partnerapi/company/detail?pc=PartnerCode&CompanyDomain=www.ibm.com&key=EncryptedKey

    The Company Detail output appears in XML as follows:

    <CompanyDetailRequest xmlns="http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/CompanyDetail.xsd">
      <CompanyID>18579882</CompanyID>
      <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=18579882&targetid=profile </ZoomCompanyUrl>
      <CompanyName>IBM Corporation</CompanyName>
      <CompanyTicker>NYSE: IBM</CompanyTicker>
      <Phone>(914) 499-1900</Phone>
      <Fax>(914) 499-2188</Fax>
      <Website>www.ibm.com</Website>
      <CompanyAddress>
        <Street>1 New Orchard Road</Street>
        <City>Armonk</City>
        <State>New York</State>
        <Zip>10504</Zip>
        <CountryCode>United States</CountryCode>
      </CompanyAddress>
      <OtherCompanyAddress>
        <Street>3039 Cornwallis Road</Street>
        <City>Research Triangle Park</City>
        <State>North Carolina</State>
        <Zip>27709</Zip>
        <CountryCode>United States</CountryCode>
      </OtherCompanyAddress>
      <OtherCompanyAddress>
        <Street>650 Harry Road</Street>
        <City>San Jose</City>
        <State>California</State>
        <Zip>95120</Zip>
        <CountryCode>United States</CountryCode>
      </OtherCompanyAddress>
      <OtherCompanyAddress>
        <Street>1701 North Street</Street>
        <City>Endicott</City>
        <State>New York</State>
        <Zip>13760</Zip>
        <CountryCode>United States</CountryCode>
      </OtherCompanyAddress>
      <OtherCompanyAddress>
        <Street>55 Second Street</Street>
        <City>San Francisco</City>
        <State>California</State>
        <Zip>94105</Zip>
        <CountryCode>United States</CountryCode>
      </OtherCompanyAddress>
      <Employees>431212</Employees>
      <Revenue>$106.9 Billion</Revenue>
      <Industry>Software Development & Design</Industry>
      <Industry>Software</Industry>
      <Industry>Personal Computers & Peripherals</Industry>
      <Industry>Computer Equipment & Peripherals</Industry>
      <Industry>Manufacturing</Industry>
      <Industry>Consumer Electronics</Industry>
      <Industry>Consumer Goods</Industry>
      <Industry> Internet Service Providers, Website Hosting & Internet-related Services </Industry>
      <Industry>Telecommunications</Industry>
      <Industry>Storage & System Management Software</Industry>
      <Industry>Content & Collaboration Software</Industry>
      <Industry>Business Intelligence Software(BI)</Industry>
      <Industry>Security software</Industry>
      <Industry>Customer Relationship Management Software(CRM)</Industry>
      <Industry>Networking Software</Industry>
      <Industry>Supply chain management Software(SCM)</Industry>
      <CompanyDescription> International Business Machines Corporation (IBM), is an information technology (IT) company. s majoroperations include Global Technology Services segment (GTS), Global Business Services segment (GBS), Software segment, Systems and Technology segment, and Global Financing segment. On January 31, 2008, the Company acquired 100% of Cognos, Inc. On April 3, 2008, IBM acquired 100% of Telelogic, AB. In July2008, the Company acquired Platform Solutions, Inc. In December 2008, its internal global logistics operations were acquired by SNCF Transport and logistics division of Geodis. In July 2009, IBM acquired Ounce Labs, Inc., a privately held company based in Waltham, Massachusetts, whose software helps companies to reduce the risks and costs associated with security and compliance concerns. In August 2009, the Company announced the launch of its China Analytics Solution Center, part of a network of global centers. </CompanyDescription>
      <MergerAcquisition>
        <CompanyID>81249685</CompanyID>
        <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=81249685&targetid=profile </ZoomCompanyUrl>
        <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=81249685&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
        <CompanyName>Initiate Systems , Inc.</CompanyName>
      </MergerAcquisition>
      <MergerAcquisition>
        <CompanyID>4669634</CompanyID>
        <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=4669634&targetid=profile </ZoomCompanyUrl>
        <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=4669634&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
        <CompanyName>BigFix , Inc.</CompanyName>
      </MergerAcquisition>
      <MergerAcquisition>
        <CompanyID>37634600</CompanyID>
        <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=37634600&targetid=profile </ZoomCompanyUrl>
        <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=37634600&pc=PartnerCode&key=EncryptedKey </CompanyDetailXmlUrl>
        <CompanyName>TeaLeaf Technology Inc</CompanyName>
      </MergerAcquisition>
      <MergerAcquisition>
        <CompanyID>344939828</CompanyID>
        <ZoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=344939828&targetid=profile </ZoomCompanyUrl>
        <CompanyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=344939828&pc=PartnerCode&key=9cdccd180df04d66ae3f3416af89a45f </CompanyDetailXmlUrl>
        <CompanyName>i2 Inc.</CompanyName>
      </MergerAcquisition>
      ...
      <CompanyRanking>Fortune 100</CompanyRanking>
      <CompanyRanking>Global 500</CompanyRanking>
      <CompanyRanking>Russell 3000</CompanyRanking>
    </CompanyDetailRequest>
    

    Output Parameters – Company Detail

    The table below shows output parameters that can be used in Company Detail queries. Parameter descriptions are grouped as follows:

    • Group - The grouping for output field permissions. The permission groups configured for a partner determine the output fields present in a response.
    • Parent Name - Name of the output element
    • Child Name - Name of a child element of a parent element specified in the parent name column
    • Notes - Information related to the output field

    Group

    Parent Name

    Child Name

    Notes

    Default

    CompanyID

    Unique identifier used by ZoomInfo for companies

    ZoomCompanyURL

    The URL to the company profile on zoominfo.com public site

    Company Name

    CompanyName

    Name of the company

    CompanyTicker

    The stock ticker for the company if available

    Phone Number

    Phone

    Primary phone number for the company

    Fax Number

    Fax

    Primary fax number for the company

    Website

    Website

    The web domain for the company in http://www.example.com format

    Primary Address

    CompanyAddress

    Contains the following child elements describing the company's primary address

    Street

    Street address for the company's primary address

    City

    City for the company's primary address

    State

    State for the company's primary address

    Zip

    Zip code of the company's primary address

    CountryCode

    Country code for the company's primary address

    Other Addresses

    OtherCompanyAddresses

    Contains the following child elements describing a company's secondary address. A company who has branches or multiple offices will commonly have multiple OtherCompanyAddresses.

    Street

    Street address for the company's other address

    City

    City for the company's other address

    State

    State for the company's other address

    Zip

    Zip code for the company's other address

    CountryCode

    Country code for the company's other address

    Revenue and Employees

    Revenue

    Approximate yearly revenue for the company

    Employees

    Approximate number of people employed by the company

    Industry

    Industry

    An industry grouping for the company. A company can have multiple industries.

    Description

    CompanyDescription

    A short paragraph describing the main purpose of the company

    M&A Info

    MergerAcquisition

    Contains the following child elements of a company that has been involved in a merger or acquisition with requested company

    CompanyID

    The ZoomInfo unique identifier for the company

    ZoomCompanyURL

    The URL to the company's zoominfo.com public site summary

    CompanyDetailXmlUrl

    API request URL for Company Detail. Returned output will be in XML format

    CompanyName

    The name of the company that was involved in M&A activity with the parent company

    Ranked Lists

    CompanyRanking

    Ranked company list that the company has appeared in (ex. Fortune 500). A company can belong to more than one ranked list.

    Key People

    KeyPerson

    Contains the following child elements of a person who is a key person at the requested company

    PersonID

    The ZoomInfo unique identifier for the person

    ZoomPersonURL

    The URL to the person's zoominfo.com public site summary

    PersonDetailXmlUrl

    API request URL for Person Detail. Returned output will be in XML format

    FirstName

    First name of the person

    LastName

    Last name of the person

    JobTitle

    Job title of the person at the requested company

    11. Company Match

    Returns match results of companies based on input criteria. The access rights for partner account restrict the available returned match output. The HTTP request for Company Match begins with the URL structure:

      http://partnerapi.zoominfo.com/partnerapi/company/match? 

    Input Parameters – Company Match

    The table below shows input parameters that can be used in Company Match queries. Parameter descriptions are grouped as follows:

    • Group - The grouping for search field permissions
    • Field Name - The name of the input parameter
    • Required - Denotes whether or not a query request requires the field
    • Value - Valid values for this input parameter
    • Notes - Information related to the input parameter
    • Key - Denotes whether or not the key generation uses the field. The order in which the parameters appear in the table is the order in which you should use them in the key. Of course, for match requests there will be one set of parameter values in the key for each input record passed into the request. Use each set of parameter values in the same order as their respective input records.

    Group

    Field Name

    Required

    Value

    Notes

    Key

    Request-level Default

    pc

    required

    Partner code (name) assigned to you

    no

    key

    required

    String consisting of 5 parameters concatenated together, and then encrypted with MD5. Parameters are:
    1) first 2 characters of every match term in each input record
    2) your partner password
    3) today's day (not padded with zero)
    4) today's month (not padded with zero)
    5) today's year (4 digit)

    no

    numMatches

    optional

    A number from 1 to 10

    Limits the match results returned to the given number of match results per input record

    no

    echoInput

    optional

    true or false

    Default value is false. If set to false, only the uniqueId for each input record is displayed in the XML output. If set to true, the uniqueId and all other input parameters for each input record are displayed in the XML output

    no

    outputFieldOptions

    optional

     

    Company Match Query has the following optional output fields:

    ·         companyPhone

    ·         companyFax

    To return one or more of these fields, specify the above output field name(s). To return multiple optional output fields, separate the values with a comma. For example, "outputFieldOptions=companyPhone,companyFax" will return companyPhone and companyFax in the XML output,

     

    Input Record-level Default

    uniqueInputId

    optional

    The unique string which will be used to identify a particular match request input record within a single match request

    no

    companyId

    optional

    Unique ZoomInfo identifier of the company to be matched by a particular input record

    yes

    name

    optional

    Name of the company to be matched by a particular input record

    yes

    domain

    optional

    The domain of the company to be matched by a particular input record

    yes

    ticker

    optional

    The ticker of the company to be matched by a particular input record

    yes

    phone (up to 5)

    optional

    A phone number of the company to be matched by a particular input record. You can enter up to 5 sets of company contact information for each input record and each set of contact information can contain any combination of phone, fax, street, city, state, zip, and/or country. For GET requests these contact parameters must be named "phone1", "phone2",... "phone5"

    no

    fax (up to 5)

    optional

    A fax number of the company to be matched by a particular input record. You can enter up to 5 sets of company contact information for each input record and each set of contact information can contain any combination of phone, fax, street, city, state, zip, and/or country. For GET requests these contact parameters must be named "fax1", "fax2",... "fax5"

    no

    street (up to 5)

    optional

    A street of the company to be matched by a particular input record. You can enter up to 5 sets of company contact information for each input record and each set of contact information can contain any combination of phone, fax, street, city, state, zip, and/or country. For GET requests these contact parameters must be named "street1", "street2",... "street5"

    no

    city (up to 5)

    optional

    A city of the company to be matched by a particular input record. You can enter up to 5 sets of company contact information for each input record and each set of contact information can contain any combination of phone, fax, street, city, state, zip, and/or country. For GET requests these contact parameters must be named "city1", "city2",... "city5"

    no

    state (up to 5)

    optional

    See list of values.

    A state of the company to be matched by a particular input record. You can enter up to 5 sets of company contact information for each input record and each set of contact information can contain any combination of phone, fax, street, city, state, zip, and/or country. For GET requests these contact parameters must be named "state1", "state2",... "state5"

    no

    zip (up to 5)

    optional

    A zip code of the company to be matched by a particular input record. You can enter up to 5 sets of company contact information for each input record and each set of contact information can contain any combination of phone, fax, street, city, state, zip, and/or country. For GET requests these contact parameters must be named "zip1", "zip2",... "zip5"

    no

    country (up to 5)

    optional

    See list of values.

    A country of the company to be matched by a particular input record. You can enter up to 5 sets of company contact information for each input record and each set of contact information can contain any combination of phone, fax, street, city, state, zip, and/or country. For GET requests these contact parameters must be named "country1", "country2",... "country5"

    no

    Example Company Match Request

    The following example shows a request for a Company Match. The input parameters include:

    • 25248427 for companyId
    • The%20Mitre%20Corporation for Name

    Note: We used %20 to denote where a space occurs in the name for the example .

    The Company Match query should be structured like this:

    http://partnerapi.zoominfo.com/partnerapi/company/match?pc=PartnerCode&companyId=25248427&Name=The%20Mitre%20Corporation&key=EncryptedKey

    The Company Match XML output would appear as follows:

    <companyMatchResponse xmlns="http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/CompanyMatchResponse.xsd">
    <matchResults>
      <companyMatchResults>
        <companyMatchResult>
          <matchCompanyInput>
            <uniqueInputId>Zoom-1</uniqueInputId>
          </matchCompanyInput>
          <companyMatches>
            <companyMatch>
              <matchConfidence>100.0</matchConfidence>
              <companyId>25248427</companyId>
              <zoomCompanyUrl> http://www.zoominfo.com/#!search/profile/company?companyId=25248427&targetid=profile </zoomCompanyUrl>
              <companyDetailXmlUrl> http://partnerapi.zoominfo.com/partnerapi/company/detail?query_type=company_detail&CompanyID=25248427&pc=PartnerCode&key=da8967da9deffabb27e882d685016f8b </companyDetailXmlUrl>
              <companyName>The MITRE Corporation</companyName>
              <website>www.mitre.org</website>
              <companyAddress>
                <street>202 Burlington Road</street>
                <city>Bedford</city>
                <state>Massachusetts</state>
                <zip>01730</zip>
                <countryCode>United States</countryCode>
              </companyAddress>
              <companyDescription> About The MITRE Corporation: MITRE is a not-for-profit national technology resource that provides systems engineering, research and development, and information technology support to the government. It operates federally funded research and development centers for the Department of Defense, the Federal Aviation Administration and the Internal Revenue Service, with principal locations in Bedford, Massachusetts, and McLean, Virginia. MITRE was founded with the purpose of conducting scientific activities "to enhance the security of the United States of America or otherwise to further the public interest ..." </companyDescription>
              <industry>Sports Teams & Leagues</industry>
              <industry>Hospitality</industry>
              <industry>Software Development & Design</industry>
              <industry>Software</industry>
            </companyMatch>
          </companyMatches>
        </companyMatchResult>
      </companyMatchResults>
    </matchResults>

    Output Parameters – Company Match

    The table below shows output parameters that can be used in Company Match queries. Parameter descriptions are grouped as follows:

    • Group - The grouping for output field permissions. The permission groups configured for a partner for company search queries determine the output fields present in a company match response.
    • Parent Name - The name of the output element
    • Child Name - The name of a child element of a parent element specified in the parent name column
    • Notes - Information related to the output field

    Group

    Parent Name

    Child Name

    Notes

    Default

    CompanyID

    Unique identifier used by ZoomInfo for companies

    ZoomCompanyUrl

    The URL to the company profile on ZoomInfo.com public site

    CompanyDetailXmlUrl

    API request URL for Company Detail. Returned output will be in XML format

    CompanyName

    Full name of the company

    CompanyTicker

    The company's public stock exchange ticker

    CompanyPhone

    Phone number for the company. Optional: This output field is optional; it won't be shown unless the 'outputFieldOptions' parameter contains this output field

    CompanyFax

    Fax number for the company. Optional: This output field is optional; it won't be shown unless the 'outputFieldOptions' parameter contains this output field

    Website

    The web domain for the company in http://www.example.com format

    CompanyAddress

    Contains the following child elements describing the company's primary address

    Street

    Street address for the company's primary address

    City

    City for the company's primary address

    State

    State for the company's primary address

    Zip

    Zip code of the company's primary address

    CountryCode

    Country code of the company's primary address

    CompanyDescription

    A short paragraph describing the main purpose of the company

    Industry

     

    An industry grouping for the company. A company can have multiple industries.

    Revenue and Employees

    Revenue

    Approximate yearly revenue for the company

    Employees

    Approximate number of people employed by the company

    Company Match – Tips

    Unlike Company Search, the Company Match query finds companies that match as closely as possible to the matching criteria provided by you. Company Match has two major categories: Single-Input Matching and Multiple-Input Matching.

    Single-Input Matching

    Single-input matching uses only one match criteria in the request, and you get zero or one matches in the response.

    Parameter

    Matches

    Notes

    name

    0 or 1

    domain

    0 or 1

    companyId

    0 or 1

    ticker

    0

    phone

    0

    fax

    0

    address

    0

    includes street, city, state, country, and zip

    Multiple-Input Matching

    With multiple-input matching, you use more than one match criteria in the request and you get 0-10 matches in the response. Multiple input matching allows for more than one company match query parameter to be specified in the request. Without the name parameter, Company Match query will not return a match.

    The Company Match query finds companies that match as closely as possible to the matching criteria.

    Parameter

    Matches

    Name + any combination of other supported company match query parameters

    0 or more

    Any combination of supported company match query parameters (no name parameter)

    0

    Hint: Provide More Matching Criteria

    The more matching criteria the better. The more criteria you specify in the request, the more accurate the match result will be.

    Hint: Specify a Company Name

    Specify a company name (if at all possible). It does not have to be the complete company name and may be an alternative name. Matching of company names is flexible but needs something to work with.

    12. Usage

    The Usage API returns your remaining usage (query limit – current query usage) and additional usage limits information of query types based on input criteria. The access rights on query types might restrict the returned output. Query usage information is only updated once a day. The HTTP request for Usage Query begins with the URL structure:

       http://partnerapi.zoominfo.com/partnerapi/usage/query?

    Note: This API call is not available for Salesforce partners.

    Input Parameters – Usage

    The following table contains the Input Parameters for Usage.

    .

    Field Name

    Required

    Notes

    pc

    yes

    Partner  Code (name) assigned to you.

    key

    yes

    The key is made up of a string consisting of parameters concatenated together, and then encrypted with MD5. Parameters are:

    • Partner password
    • Today's day of the month (not padded with zero)
    • Today's month (not padded with zero)
    • Today's year (4 digits)

    outputType

    no

    The output type of the response (case insensitive): xml or json

    queryTypeOptions

    no

    The following are available options (case insensitive):

    • people_search_query
    • person_detail
    • person_match
    • company_search_query
    • company_detail
    • company_match

    Example Usage Query

    The following shows an example Usage query for company_search_query and person_detail:

    http://partnerapi.zoominfo.com/partnerapi/usage/query?pc=PartnerCode& queryTypeOptions=company_search_query,person_detail&key=EncryptedKey

    Example XML output:

    <?xml version="1.0" encoding="utf-8"?>
    <usageQueryResponse
    xmlns="http://partnerapi.zoominfo.com/partnerapistatic/xsd/V1/UsageQueryResponse.xsd">
      <inputParameters>
        <parameter>
          <name>queryTypeOptions</name>
          <value>company_search_query,person_detail</value>
        </parameter>
      </inputParameters>
      <queryResult>
        <overallUsageLimit>
          <currentQueryUsage>1000</currentQueryUsage>
          <usageRemaining>4000</usageRemaining>
          <queryLimit>5000</queryLimit>
          <limitTerms>Per Month</limitTerms>
          <limitType>Soft Limit</limitType>
        </overallUsageLimit>
        <queryTypeUsageLimits>
          <queryType>company_search_query</queryType>
          <queryTypeQueryLimit>
            <currentQueryUsage>1500</currentQueryUsage>
            <usageRemaining>3500</usageRemaining>
            <queryLimit>5000</queryLimit>
            <limitTerms>Per Month</limitTerms>
            <limitType>Soft Limit</limitType>
          </queryTypeQueryLimit>
          <resultsPerQueryLimit>5000</resultsPerQueryLimit>
        </queryTypeUsageLimits>
        <queryTypeUsageLimits>
          <queryType>person_detail</queryType>
          <queryTypeQueryLimit>
            <currentQueryUsage>2000</currentQueryUsage>
            <usageRemaining>3000</usageRemaining>
            <queryLimit>5000</queryLimit>
            <limitTerms>Per Month</limitTerms>
            <limitType>Soft Limit</limitType>
          </queryTypeQueryLimit>
          <resultsPerQueryLimit>1</resultsPerQueryLimit>
        </queryTypeUsageLimits>
      </queryResult>
    </usageQueryResponse>

    Output Parameters – Usage

    The following table contains the Output Parameters for Usage.

    Group

    Parent Name

    Child Name

    Notes

    Default

    overallUsageLimit

    Current limit for overall use of APIs

    currentQueryUsage

    Amount of queries used

    usageRemaining

    Amount of queries remaining

    queryLimit

    Pre-established limit on API queries

    limitTerms

    Terms of limit. Ex. per month, per quarter, or per year.

    limitType

    Type of limit. Ex. hard limit, soft limit

    Optional

    people_search_query

     

    Usage information on Person Search queries.

    currentQueryUsage

    Amount of queries used

    usageRemaining

    Amount of queries remaining

    queryLimit

    Pre-established limit on API queries

    limitTerms

    Terms of limit. Ex. per month, per quarter, or per year.

    limitType

    Type of limit. Ex. hard limit, soft limit

    resultsPerQueryLimit

    Limit to the amount of results that will appear on a page.

    person_detail

     

    Usage information on Person Detail queries.

    currentQueryUsage

    Amount of queries used

    usageRemaining

    Amount of queries remaining

    queryLimit

    Pre-established limit on API queries

    limitTerms

    Terms of limit. Ex. per month, per quarter, or per year.

    limitType

    Type of limit. Ex. hard limit, soft limit

    resultsPerQueryLimit

    1

    person_match

     

    Usage information on Person Match queries

    currentQueryUsage

    Amount of queries used

    usageRemaining

    Amount of queries remaining

    queryLimit

    Pre-established limit on API queries

    limitTerms

    Terms of limit. Ex. per month, per quarter, or per year.

    limitType

    Type of limit. Ex. soft limit

    resultsPerQueryLimit

    10

    company_search_query

     

    Usage information on Company Search queries

    currentQueryUsage

    Amount of queries used

    usageRemaining

    Amount of queries remaining

    queryLimit

    Pre-established limit on API queries

    limitTerms

    Terms of limit. Ex. per month, per quarter, or per year.

    limitType

    Type of limit. Ex. hard limit, soft limit

    resultsPerQueryLimit

    Limit to the amount of results that will appear on a page.

    company_detail

     

    Usage information on Company Detail queries

    currentQueryUsage

    Amount of queries used

    usageRemaining

    Amount of queries remaining

    queryLimit

    Pre-established limit on API queries

    limitTerms

    Terms of limit. Ex. per month, per quarter, or per year.

    limitType

    Type of limit. Ex. hard limit, soft limit

    resultsPerQueryLimit

    1

    company_match

     

    Usage information on Company Match queries

    currentQueryUsage

    Amount of queries used

    usageRemaining

    Amount of queries remaining

    queryLimit

    Pre-established limit on API queries

    limitTerms

    Terms of limit. Ex. per month, per year.

    limitType

    Type of limit. Ex. hard limit, soft limit

    resultsPerQueryLimit

    10

    13. Appendix

    The following section provides information on the legacy APIs with old style URL construction.

    Legacy URLs

    There are legacy URLs that will still work, but we are deprecating all the old URLs. We strongly recommend that you use the new URLs at your earliest convenience.

    Old Style

    http://partnerapi.zoominfo.com/partnerapi/xmloutput.aspx?query_type=people_search_query>

    This old style is deprecated. Switch to the new style

    New Style

    http://partnerapi.zoominfo.com/partnerapi/person/search?

    Use this new style.

    ZoomInfo Pricing

    Untitled Document

    A Plan to Suit Your Needs.

    Grow your business with a scalable pricing plan.

    Save up to 20% with an annual plan
    COMMUNITY

    FREE

     

    10 Contacts
    per month

    Select Plan
    CONNECT BASIC

    $69.9559.95/month

    ($719.40 billed annually)

     

    80 Contacts
    per month

    Select Plan Select Plan
    CONNECT GOLD

    $109.9584.95/month

    ($1019.40 billed annually)

     

    150 Contacts
    per month

    Select Plan Select Plan
    CONNECT PLATINUM

    $139.9599.95/month

    ($1199.40 billed annually)

     

    250 Contacts
    per month

    Select Plan Select Plan
    PRO

    Call Us

    1-866-904-9666

    Unlimited
    contacts

    Select Plan
    Need customized pricing? Contact us to learn more.

    Common Questions

    Who is ZoomInfo?

    ZoomInfo is the most comprehensive source of business information. Our information can be accessed from searches on ZoomInfo.com or from our subscription products. This information is gathered from the same publicly available web sources that are searched by other major search engines like Yahoo and Google, and accessible to any person surfing the web.

    Where does ZoomInfo gets its information?

    The short answer is that ZoomInfo found it on the public web. The longer answer is that the information making up a ZoomInfo profile was found on one, dozens, or even hundreds of public sources across the Internet, and intelligently assembled into a single, concise professional profile using ZoomInfo's proprietary technology. You will see a date associated with every online source, which will let you know how recently the text was available on a public web source.

    How can I benefit from ZoomInfo products the most?

    We have seen that users who use ZoomInfo on a recurring basis benefit from our products the most. ZoomInfo updates its database constantly, and each contact's information is updated at least once in 90 days. A user can take advantage of features, such as alert and saved searches, to keep a track on any change that might happen in the contact's information that you are interested in. This is especially useful if you want to achieve a high ROI with your email marketing campaigns or if you want to use your time effectively while cold calling your prospects.

    What are alerts and how can I use them?

    Alerts allow you to follow updates made to profiles in the database. You can set alerts on a single person's profile, or on specific search criteria to receive notification when updates have occurred. For example, if a VP of Marketing has left her existing company to join a different one, you will see an alert on the profile the next time you log in to your ZoomInfo account.

    More Articles...

    1. SEO Profile Video
    2. Iframe Test
    3. Tech Overlays
    4. Sales 2.0 2014 Conference

    Subcategories