ZoomInfo Search API
The Search API from ZoomInfo — 5 operation(s) for search.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/zoominfo-search-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
OpenAPI Specification
openapi: 3.2.0
info:
title: Data API V1 Search API
version: '1.0'
contact:
name: ZoomInfo Customer Support
email: help@zoominfo.com
description: The Data API
servers:
- url: https://api.zoominfo.com/gtm
description: Base URL for the Data API
security:
- OAuth2Auth: []
tags:
- name: Search
paths:
/data/v1/contacts/search:
post:
operationId: SearchInterface_searchContact
summary: Search Contacts
description: 'Returns a list of Contacts from ZoomInfo''s data that meet the specified search criteria.
Input parameters may require specific values. You can use the [Lookup Data](ref:lookupinterface_lookup)
endpoint to retrieve the list of possible values
The Search Contacts API does not return emails, phone numbers, or any other data that can be used to engage with
the contacts in your results, but the results do include hints for what data ZoomInfo has for a specific contact.
To get the additional data for contacts, including emails or phone numbers, use the
[Enrich Contact API](ref:enrichinterface_enrichcontact)
With reference to ZoomInfo''s [Credit Usage and Limits](doc:credit-usage-and-limits), this endpoint does not
consume any credits nor do contacts returned count towards record limits, but each request will increment against your
request limits.'
parameters:
- name: page[number]
in: query
required: false
description: 'The page of results that you want to retrieve. If not provided, the first page
of results will be returned. Use in connection with `page[size]` to handle large result sets.
Example: `page[number]=2&page[size]=25` will return the second page of result (results 26-50 based
on the `sort` value).'
schema:
type: integer
format: int32
minimum: 1
explode: false
- name: page[size]
in: query
required: false
description: 'Sets the number of records to return per page. If not provided, the default is 25 records per
page. Valid values for page size are any integer from 1 to 100.'
schema:
type: integer
format: int32
minimum: 1
maximum: 100
explode: false
- name: sort
in: query
required: false
description: 'Sort results by the specified output field. Valid values are contactAccuracyScore, lastName, companyName,
hierarchy, sourceCount, lastMentioned, and relevance. Add minus sign (''-'') for descending order. The default
value if not provided is sorting by relevance in descending order `-relevance`
Examples:
- `lastName` will sort results by contact last name in ascending alphabetical order.
- `-lastMentioned` will sort results in descending order (most recently to least recently mentioned)
by the `lastMentioned` date for each contact'
schema:
type: string
explode: false
responses:
'200':
description: Success
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ContactSearchResponse'
examples:
Contact search by companyName, firstName, and lastName:
summary: Contact search by companyName, firstName, and lastName
description: This example demonstrates how to search for contacts using the ZoomInfo API utilizing multiple input fields. In this example, the companyName, firstName, and lastName fields are used to find a list of matching contacts.
value:
data:
- attributes:
company:
id: 344589814
name: ZoomInfo
contactAccuracyScore: 95
directPhoneDoNotCall: false
firstName: Filip
hasCompanyCountry: true
hasCompanyEmployeeCount: true
hasCompanyIndustry: true
hasCompanyPhone: true
hasCompanyRevenue: true
hasCompanyState: true
hasCompanyStreet: true
hasCompanyZipCode: true
hasDirectPhone: false
hasEmail: true
hasMobilePhone: true
hasSupplementalEmail: true
jobTitle: Chief Technology Officer
lastName: Popovic
lastUpdatedDate: '2025-04-04T18:13:00Z'
mobilePhoneDoNotCall: false
validDate: '2024-11-14T22:29:00Z'
id: '4191419698'
type: Contact
links:
first: /data/v1/contacts/search?page[number]=1&page[size]=25
last: /data/v1/contacts/search?page[number]=1&page[size]=25
meta:
page:
number: 1
total: 1
totalResults: 1
Contact search by personId:
summary: Contact search by personId
description: This example demonstrates how to search for contacts using the ZoomInfo API utilizing single field. In this example, the personId field is used to find a matching contact.
value:
data:
- attributes:
company:
id: 344589814
name: ZoomInfo
contactAccuracyScore: 94
directPhoneDoNotCall: false
firstName: Henry
hasCompanyCountry: true
hasCompanyEmployeeCount: true
hasCompanyIndustry: true
hasCompanyPhone: true
hasCompanyRevenue: true
hasCompanyState: true
hasCompanyStreet: true
hasCompanyZipCode: true
hasDirectPhone: true
hasEmail: true
hasMobilePhone: false
hasSupplementalEmail: true
jobTitle: Chief Executive Officer & Board Member
lastName: Schuck
lastUpdatedDate: '2024-10-21T14:05:00Z'
middleName: L.
mobilePhoneDoNotCall: false
validDate: '2024-11-14T22:29:00Z'
id: '1260398587'
type: Contact
links:
first: /data/v1/contacts/search?page[number]=1&page[size]=25
last: /data/v1/contacts/search?page[number]=1&page[size]=25
meta:
page:
number: 1
total: 1
totalResults: 1
'400':
description: Bad Request
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'401':
description: Unauthorized
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'403':
description: Forbidden
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'429':
description: Too Many Requests
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
tags:
- Search
requestBody:
required: true
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ContactSearchRequest'
examples:
Contact search by companyName, firstName, and lastName:
summary: Contact search by companyName, firstName, and lastName
description: This example demonstrates how to search for contacts using the ZoomInfo API utilizing multiple input fields. In this example, the companyName, firstName, and lastName fields are used to find a list of matching contacts.
value:
data:
attributes:
companyName: ZoomInfo
firstName: Filip
lastName: Popovic
type: ContactSearch
Contact search by personId:
summary: Contact search by personId
description: This example demonstrates how to search for contacts using the ZoomInfo API utilizing single field. In this example, the personId field is used to find a matching contact.
value:
data:
attributes:
personId: '1260398587'
type: ContactSearch
description: The request body containing contact search criteria.
security:
- OAuth2Auth:
- api:data:contact
x-additional-content-types:
- application/json
x-api-roles:
- fea:zia
- fea:api
x-api-role-requirement: ANY_REQUIRED
/data/v1/companies/search:
post:
operationId: SearchInterface_searchCompany
summary: Search Companies
description: 'Returns a list of Companies from ZoomInfo''s data that meet the specified search criteria.
Input parameters may require specific values. You can use the [Lookup Data](ref:lookupinterface_lookup)
endpoint to retrieve the list of possible values
The Search Companies API only returns basic information about the company: including name, limited location details,
website, and few other basic data points. To get the additional data for companies in your results use the
[Enrich Company API](ref:enrichinterface_enrichcompany)
With reference to ZoomInfo''s [Credit Usage and Limits](doc:credit-usage-and-limits), this endpoint does not
consume any credits nor do copmanies returned count towards record limits, but each request will increment against your
request limits.'
parameters:
- name: page[number]
in: query
required: false
description: 'The page of results that you want to retrieve. If not provided, the first page
of results will be returned. Use in connection with `page[size]` to handle large result sets.
Example: `page[number]=2&page[size]=25` will return the second page of result (results 26-50 based
on the `sort` value).'
schema:
type: integer
format: int32
minimum: 1
explode: false
- name: page[size]
in: query
required: false
description: 'Sets the number of records to return per page. If not provided, the default is 25 records per
page. Valid values for page size are any integer from 1 to 100.'
schema:
type: integer
format: int32
minimum: 1
maximum: 100
explode: false
- name: sort
in: query
required: false
description: "Sort results by the specified output field. Valid values are name, employeeCount, and revenue. \nAdd minus sign ('-') for descending order. The default sort if not provided is to sort the results \nby revenue in descending order `-revenue`\n\nExamples:\n- `name` will sort results by company name in ascending alphabetical order.\n- `-employeeCount` will sort results in descending order (from company with the most number of employees\nto the company with the least number of employees)"
schema:
type: string
explode: false
responses:
'200':
description: Success
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/CompanySearchResponse'
examples:
Company search by companyName for privileged customer:
summary: Company search by companyName for privileged customer
description: This example demonstrates how to search for companies using the ZoomInfo API utilizing input field. In this example, the companyName field is used to find a list of matching companies.
value:
data:
- attributes:
logo: https://res.cloudinary.com/zoominfo-com/image/upload/w_100,h_100,c_fit/zoominfo.com
name: ZoomInfo
website: www.zoominfo.com
id: '344589814'
type: Company
- attributes:
name: Zoominfo Com C Peter Taflan Marketing Communications
id: '1307620605'
type: Company
links:
first: /data/v1/companies/search?page#[number]=1&page#[size]=25
last: /data/v1/companies/search?page#[number]=1&page#[size]=25
meta:
page:
number: 1
total: 2
totalResults: 2
Company search by metro region, industry codes including pagination and sorting url params:
summary: Company search by metro region, industry codes including pagination and sorting url params
description: This example demonstrates how to search for companies using the ZoomInfo API utilizing multiple input fields. In this example, the metroRegion and industryCodes field is used to find a list of matching companies on second page with two records per page sorted by name ascending.
value:
data:
- attributes:
name: 123cd.org
id: '57295081'
type: Company
- attributes:
name: 12Kerala
id: '352306193'
type: Company
links:
first: uri=/data/v1/companies/search?page[number]=1&page[size]=2
last: uri=/data/v1/companies/search?page[number]=1426&page[size]=2
next: uri=/data/v1/companies/search?page[number]=4&page[size]=2
prev: uri=/data/v1/companies/search?page[number]=2&page[size]=2
meta:
page:
number: 2
total: 2
totalResults: 2845
'400':
description: Bad Request
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'401':
description: Unauthorized
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'403':
description: Forbidden
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'429':
description: Too Many Requests
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
tags:
- Search
requestBody:
required: true
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/CompanySearchRequest'
examples:
Company search by companyName for privileged customer:
summary: Company search by companyName for privileged customer
description: This example demonstrates how to search for companies using the ZoomInfo API utilizing input field. In this example, the companyName field is used to find a list of matching companies.
value:
data:
attributes:
companyName: Zoominfo
type: CompanySearch
Company search by metro region, industry codes including pagination and sorting url params:
summary: Company search by metro region, industry codes including pagination and sorting url params
description: This example demonstrates how to search for companies using the ZoomInfo API utilizing multiple input fields. In this example, the metroRegion and industryCodes field is used to find a list of matching companies on second page with two records per page sorted by name ascending.
value:
data:
attributes:
metroRegion: usa.california.sanfrancisco
industryCodes: education.university
type: CompanySearch
description: The request body containing company search criteria.
security:
- OAuth2Auth:
- api:data:company
x-additional-content-types:
- application/json
x-api-roles:
- fea:zia
- fea:api
x-api-role-requirement: ANY_REQUIRED
/data/v1/intent/search:
post:
operationId: SearchInterface_searchIntent
summary: Search Intent
description: "Returns a list of Intent Signals from ZoomInfo's data that meet the specified search criteria. It is required \nthat every request include at least 1 and up to 50 intent topics in the request.\n\nIntent data is online behavior-based activity across the internet that links prospective buyers (companies) to a topic.\nIntent Signals are the way ZoomInfo tracks intent data and can be used to indicate recent content consumption for a specific\ntopic by employees at a company. Key terminology for Intent Signals includes:\n\n* **Topic** - A business subject or technology area mapped to a curated collection of keywords and search terms. \nWhen companies research content containing these keywords, it generates intent signals that indicate their buying interest\n* **Signal Score** - Indicates the level of a company's interest in a topic based on how recent content consumption \ncompares to an historical baseline\n* **Audience Strength** - Indicates the size of the group at the company that is conducting the research\n\nUse Search Intent to find Intent Signals across all ZoomInfo companies. To find Intent Signals for a specific company, use the\n[Enrich Intent](ref:enrichinterface_enrichintent) endpoint.\n\nInput parameters may require specific values. You can use the [Lookup Data](ref:lookupinterface_lookup)\nendpoint to retrieve the list of possible values.\n\nWith reference to ZoomInfo's [Credit Usage and Limits](doc:credit-usage-and-limits), this endpoint does not\nconsume any credits, but each Intent Signal returned in the results is counted as a Record and a successful response\nwill count as a Request credit."
parameters:
- name: page[number]
in: query
required: false
description: 'The page of results that you want to retrieve. If not provided, the first page
of results will be returned. Use in connection with `page[size]` to handle large result sets.
Example: `page[number]=2&page[size]=25` will return the second page of result (results 26-50 based
on the `sort` value).'
schema:
type: integer
format: int32
minimum: 1
explode: false
- name: page[size]
in: query
required: false
description: 'Sets the number of records to return per page. If not provided, the default is 25 records per
page. Valid values for page size are any integer from 1 to 100.'
schema:
type: integer
format: int32
minimum: 1
maximum: 100
explode: false
- name: sort
in: query
required: false
description: 'Sort results by the specified output field. Valid values are `signalDate`, `companyName`, `signalScore`,
`category`, `topic`, and `audienceStrength`. Add minus sign (''-'') for descending order. The default,
if not provided, is to sort the results by `topic` name in descending order (`-topic`)
Examples:
- `companyName` will sort results by company name in ascending alphabetical order.
- `-signalDate` will sort results in descending order by signal date (from most recent signals to
the oldest signals)'
schema:
type: string
explode: false
responses:
'200':
description: Success
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/IntentSearchResponse'
examples:
Intent search by various attributes:
summary: Intent search by various attributes
description: This example demonstrates how to search for intent topics using the ZoomInfo API utilizing input fields.
value:
data:
- attributes:
audienceStrength: B
category: Cloud
recommendedContacts:
- id: '4191419698'
firstName: Filip
lastName: Popovic
jobTitle: Chief Technology Officer
companyName: ZoomInfo
- id: '1260398587'
firstName: John
lastName: Doe
jobTitle: Software Engineer
companyName: TechCorp
signalDate: '2025-05-24T00:00:00Z'
signalScore: 82
spikesInDateRange: 1
topic: Cloud Applications
id: vopctz9gg4g8#47028048#20250524
type: Intent
links:
first: /data/v1/intents/search?page#[number]=1&page#[size]=25
last: /data/v1/intents/search?page#[number]=1&page#[size]=25
meta:
page:
number: 1
total: 1
totalResults: 1
'400':
description: Bad Request
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'401':
description: Unauthorized
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'403':
description: Forbidden
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'429':
description: Too Many Requests
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
tags:
- Search
requestBody:
required: true
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/IntentSearchRequest'
examples:
Intent search by various attributes:
summary: Intent search by various attributes
description: This example demonstrates how to search for intent topics using the ZoomInfo API utilizing input fields.
value:
data:
attributes:
topics:
- Cloud Applications
signalScoreMin: 80
signalScoreMax: 100
audienceStrengthMin: C
audienceStrengthMax: A
metroRegion: usa.california.sanfrancisco
industryCodes: education.university
type: IntentSearch
description: The request body containing intent search criteria.
security:
- OAuth2Auth:
- api:data:intent
x-additional-content-types:
- application/json
x-api-roles:
- fea:zia
- fea:api
x-api-role-requirement: ANY_REQUIRED
/data/v1/news/search:
post:
operationId: SearchInterface_searchNews
summary: Search News
description: 'Returns a list of News articles from ZoomInfo''s data that meet the specified search criteria. All inputs are optional,
but at least one input must be set to get a successful response.
Input parameters may require specific values. You can use the [Lookup Data](ref:lookupinterface_lookup)
endpoint to retrieve the list of possible values.
Use Search News to find News articles across all ZoomInfo companies, if you want to get News articles for a specific ZoomInfo company,
use the [Enrich News](ref:enrichinterface_enrichnews) endpoint.
With reference to ZoomInfo''s [Credit Usage and Limits](doc:credit-usage-and-limits), this endpoint does not
consume any Credits. Each News article returned in the results does count towards the customer''s Record Limit
and a successful response will count towards the Request Limit (e.g. for a response that returns 10 news articles, 10 Records will
be counted and 1 Request will be counted)'
parameters:
- name: page[number]
in: query
required: false
description: 'The page of results that you want to retrieve. If not provided, the first page
of results will be returned. Use in connection with `page[size]` to handle large result sets.
Example: `page[number]=2&page[size]=25` will return the second page of result (results 26-50 based
on the `sort` value).'
schema:
type: integer
format: int32
minimum: 1
explode: false
- name: page[size]
in: query
required: false
description: 'Sets the number of records to return per page. If not provided, the default is 25 records per
page. Valid values for page size are any integer from 1 to 100.'
schema:
type: integer
format: int32
minimum: 1
maximum: 100
explode: false
responses:
'200':
description: Success
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/NewsSearchResponse'
examples:
Search news articles by category and publish date:
summary: Search news articles by category and publish date
description: This example demonstrates how to search for news articles using the ZoomInfo API utilizing categories, pageDateMin and pageDateMax. In this example, the categories field is used to filter articles related to specific topics such as 'PRODUCT' and 'PERSON', and the publish date range is set from January 1, 2024, to December 31, 2024. The response includes articles that match these criteria, with pagination enabled to retrieve results in chunks of two articles per page.
value:
data:
- type: News
id: article-1
attributes:
domain: techcrunch.com
title: ZoomInfo Launches New AI Product
url: https://www.techcrunch.com/articles/zoominfo-launch-ai-product
imageUrl: https://www.techcrunch.com/images/zoominfo-launch.jpg
pageDate: '2024-05-20T14:00:00Z'
categories:
- PRODUCT
description: ZoomInfo has launched a new AI-driven product to enhance go-to-market strategies.
company:
- id: 344589814
name: ZoomInfo
- type: News
id: article-2
attributes:
domain: businesswire.com
title: ZoomInfo Appoints New CTO
url: https://www.businesswire.com/news/zoominfo-new-cto
imageUrl: https://www.businesswire.com/images/cto-hire.jpg
pageDate: '2024-03-12T09:30:00Z'
categories:
- PERSON
description: ZoomInfo has appointed Jane Doe as its new Chief Technology Officer.
company:
- id: 344589814
name: ZoomInfo
meta:
page:
number: 1
total: 1
totalResults: 2
links:
first: /data/v1/news/search?page[number]=1&page[size]=2
last: /data/v1/news/search?page[number]=1&page[size]=2
'400':
description: Bad Request
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'401':
description: Unauthorized
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'403':
description: Forbidden
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
'429':
description: Too Many Requests
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ZoomInfo.Core.Foundations.ErrorResponseModel'
tags:
- Search
requestBody:
required: true
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/NewsSearchRequest'
examples:
Search news articles by category and publish date:
summary: Search news articles by category and publish date
description: This example demonstrates how to search for news articles using the ZoomInfo API utilizing categories, pageDateMin and pageDateMax. In this example, the categories field is used to filter articles related to specific topics such as 'PRODUCT' and 'PERSON', and the publish date range is set from January 1, 2024, to December 31, 2024. The response includes articles that match these criteria, with pagination enabled to retrieve results in chunks of two articles per page.
value:
data:
type: NewsSearch
attributes:
categories:
- PRODUCT
- PERSON
pageDateMin: '2024-01-01'
pageDateMax: '2024-12-31'
description: The request body containing news search criteria.
security:
- OAuth2Auth:
- api:data:news
x-additional-content-types:
- application/json
x-api-roles:
- fea:zia
- fea:api
x-api-role-requirement: ANY_REQUIRED
/data/v1/scoops/search:
post:
operationId: SearchInterface_searchScoop
summary: Search Scoops
description: "Returns a list of Scoops from ZoomInfo's data that meet the specified search criteria. \n\nScoops are real-time business intelligence signals that provide time
# --- truncated at 32 KB (120 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/zoominfo/refs/heads/main/openapi/zoominfo-search-api-openapi.yml