ZoomInfo Enrich API
The Enrich API from ZoomInfo — 9 operation(s) for enrich.
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-enrich-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 Enrich 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: Enrich
paths:
/data/v1/contacts/enrich:
post:
operationId: EnrichInterface_enrichContact
summary: Enrich Contacts
description: "Enrich Contacts can be used to retrieve detailed information about up to 25 individual contact records.\nBest practice is to first use the [Search Contacts](ref:searchinterface_searchcontact) to identify the records \nyou want to enrich, and then use the Contact IDs as the input to specify the correct records. If your workflow does not \nsupport a two stage retrieval using both Search and Enrich endpoints, you can query the Contact Enrich Endpoint with more \nextensive input information and our system will provide the best match available to the input. The more details you provide \nthe more likely we are to provide the correct match. \n\nOnce you have indicated which records you want to enrich, you must then select which fields you want to return for the \nrecords using the `outputFields` list. For more details about all of the available output fields you can select, please \nuse the [Lookup Enrich](ref:lookupenrichinterface_lookupenrich) endpoint (`filter[entity]=contact` and `filter[fieldType]=output`). \nThis will provide a description of each available field, as well as whether or not your account has access to this field. \nIf you do not have access to a field that you need, please contact your ZoomInfo Account Manager for purchasing options. \n\nYou can also use the `requiredFields` list to indicate which fields must be available for output in order to return\na record. For example, if you include `jobTitle` in `requiredFields` we will not return a contact for which we do not \nhave a job title recorded, even if it is a perfect match for the input criteria you provided. \n\nEach record returned by this endpoint will charge a credit from your account, unless that record is already under management \n(see [Credit Usage and Limits Guide](doc:credit-usage-and-limits) for more details). If we fail to find the record and return \n“No match” or if we return an error code a credit will not be charged."
parameters: []
responses:
'200':
description: Success
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ContactEnrichResponse'
examples:
Enrich Contact by Person ID Using Output Fields and Required Fields for a Full Match:
summary: Enrich Contact by Person ID Using Output Fields and Required Fields for a Full Match
description: This example demonstrates how to enrich a single contact using a unique personId. The request specifies a set of outputFields to return, including email, company name, and movement status, while ensuring that required fields like id and company name are always included. This allows for precise and efficient contact data retrieval. Up to 25 contacts can be enriched in a single request.
value:
data:
- attributes:
company:
id: 346572700
name: ZoomInfo
email: henry@zoominfo.com
hasCanadianEmail: false
personHasMoved: 'No'
id: '344589814'
meta:
input:
personId: 4191419698
matchStatus: FULL_MATCH
type: Contact
Enrich Contact by Person ID Using Various Company Output Fields and Required Fields for a Full Match:
summary: Enrich Contact by Person ID Using Various Company Output Fields and Required Fields for a Full Match
description: This example demonstrates how to enrich a single contact using a unique personId. The request specifies a set of outputFields related to the contact's company to return, including company name, company logo, and company revenue, while ensuring that required fields like id and company name are always included.
value:
data:
- attributes:
company:
city: Vancouver
country: United States
description: ZoomInfo is the go-to-market platform that helps businesses find, acquire, and grow customers. ZoomInfo is the most comprehensive source of business information on people and companies in the world. ZoomInfo is used by sales and marketing professionals to find leads, recruiters to uncover talent and by business professionals to find detailed information on people and companies.
employeeCount: 3508
employeeRange: 1,000 - 5,000
fax: (617) 507-8187
id: 344589814
industries:
- Software
- Business Intelligence (BI) Software
logo: https://res.cloudinary.com/zoominfo-com/image/upload/w_100,h_100,c_fit/zoominfo.com
naicsCodes:
- id: '51'
name: Information
- id: '516'
name: Broadcasting and Content Providers
- id: '5162'
name: Media Streaming Distribution Services, Social Networks, and Other Media Networks and Content Providers
- id: '51621'
name: Media Streaming Distribution Services, Social Networks, and Other Media Networks and Content Providers
- id: '517'
name: Telecommunications
- id: '5171'
name: Wired and Wireless Telecommunications (except Satellite)
- id: '51711'
name: Wired and Wireless Telecommunications Carriers (except Satellite)
- id: '54'
name: Professional, Scientific, and Technical Services
- id: '541'
name: Professional, Scientific, and Technical Services
- id: '5415'
name: Computer Systems Design and Related Services
- id: '54151'
name: Computer Systems Design and Related Services
- id: '541511'
name: Custom Computer Programming Services
- id: '511'
name: Publishing Industries (except Internet)
- id: '5112'
name: Software Publishers
- id: '51121'
name: Software Publishers
- id: '511210'
name: Software Publishers
name: ZoomInfo
phone: (866) 904-9666
primaryIndustry:
- Software
- Business Intelligence (BI) Software
revenue: $1.2 Billion
revenueNumeric: 1214300000
revenueRange: $1 bil. - $5 bil.
sicCodes:
- id: '73'
name: Business Services
- id: '737'
name: Computer Programming, Data Processing, And Other Computer Related Services
- id: '7372'
name: Prepackaged Software
- id: '738'
name: Miscellaneous Business Services
- id: '7389'
name: Business Services, Not Elsewhere Classified
- id: '7371'
name: Computer Programming Services
socialMediaUrls:
- followerCount: '128080'
type: LINKED_IN
url: http://www.linkedin.com/company/zoominfo
- followerCount: '14415'
type: TWITTER
url: http://www.twitter.com/zoominfo
- type: FACEBOOK
url: http://www.facebook.com/109325735758217
state: Washington
street: 805 Broadway St Ste 900
ticker: NASDAQ:GTM
type: PUBLIC
website: www.zoominfo.com
zipCode: '98660'
email: henry@zoominfo.com
hasCanadianEmail: false
personHasMoved: 'No'
id: '344589814'
meta:
input:
personId: 4191419698
matchStatus: FULL_MATCH
type: Contact
Enrich Multiple Contacts Using Required Fields and Output Fields for a Full Match.:
summary: Enrich Multiple Contacts Using Required Fields and Output Fields for a Full Match.
description: This example demonstrates how to enrich multiple contacts by using a mix of identifiers—including a combination of firstName, lastName, and companyName, as well as a direct personId. The request specifies a wide range of outputFields, such as email, job title, address, company details, and regulatory flags. This allows for detailed enrichment of each contact. The response returns enriched data for each matched contact, and up to 25 contacts can be processed in a single request.
value:
data:
- attributes:
company:
id: 346572700
name: ZoomInfo
employeeCount: 3508
primaryIndustry:
- Software
- Business Intelligence Software
country: United States
email: henry@zoominfo.com
hasCanadianEmail: false
jobTitle: Chief Executive Officer & Board Member
directPhoneDoNotCall: false
directPhoneAlt:
- value: +1-360-555-1234
source: waterfall
mobilePhoneAlt:
- value: +1-360-555-5678
source: waterfall
emailAlt:
- value: henry.schuck@zoominfo.com
source: waterfall
withinCalifornia: false
withinCanada: false
withinEu: false
metroArea: Boston
personHasMoved: 'No'
region: Massachusetts
state: Massachusetts
street: 404 Wyman St
zipCode: '02451'
id: '344589814'
meta:
input:
companyName: zoominfo
firstName: henry
lastName: schuck
matchStatus: FULL_MATCH
type: Contact
- attributes:
city: Bethesda
company:
id: 346572700
name: ZoomInfo
employeeCount: 3508
primaryIndustry:
- Software
- Business Intelligence Software
country: United States
directPhoneDoNotCall: false
email: filip@discoverorg.com
firstName: Filip
hasCanadianEmail: false
jobTitle: Chief Technology Officer
managementLevel:
- C-Level
metroArea: Washington
personHasMoved: Uncertain
region: Maryland
state: Maryland
street: 7700 Old Georgetown Rd 5th Fl
zipCode: '20814'
id: '234343645'
meta:
input:
personId: 4191419698
matchStatus: FULL_MATCH
type: Contact
Enrich Contact by Person ID Using Output Fields for a No Match:
summary: Enrich Contact by Person ID Using Output Fields for a No Match
description: This example demonstrates how to enrich a single contact using a unique personId. The request specifies a set of outputFields to return, including email, company name, and movement status. The response is a no match response for the contact criteria requested.
value:
data:
- id: '0'
meta:
input:
personId: 0
matchStatus: NO_MATCH
type: NoMatch
'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:
- Enrich
requestBody:
required: true
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/ContactEnrichRequest'
examples:
Enrich Contact by Person ID Using Output Fields and Required Fields for a Full Match:
summary: Enrich Contact by Person ID Using Output Fields and Required Fields for a Full Match
description: This example demonstrates how to enrich a single contact using a unique personId. The request specifies a set of outputFields to return, including email, company name, and movement status, while ensuring that required fields like id and company name are always included. This allows for precise and efficient contact data retrieval. Up to 25 contacts can be enriched in a single request.
value:
data:
attributes:
matchPersonInput:
- personId: 4191419698
outputFields:
- id
- email
- personHasMoved
- hasCanadianEmail
- companyName
requiredFields:
- id
- companyName
type: ContactEnrich
Enrich Contact by Person ID Using Various Company Output Fields and Required Fields for a Full Match:
summary: Enrich Contact by Person ID Using Various Company Output Fields and Required Fields for a Full Match
description: This example demonstrates how to enrich a single contact using a unique personId. The request specifies a set of outputFields related to the contact's company to return, including company name, company logo, and company revenue, while ensuring that required fields like id and company name are always included.
value:
data:
attributes:
matchPersonInput:
- personId: 4191419698
outputFields:
- id
- email
- personHasMoved
- companyName
- companyDescriptionList
- companyPhone
- companyFax
- companyStreet
- companyCity
- companyState
- companyZipCode
- companyCountry
- companyLogo
- companySicCodes
- companyNaicsCodes
- contactAccuracyScore
- companyWebsite
- companyRevenue
- companyRevenueNumeric
- companyEmployeeCount
- companyType
- companyTicker
- companyRanking
- companySocialMediaUrls
- companyPrimaryIndustry
- companyIndustries
- companyRevenueRange
- companyEmployeeRange
requiredFields:
- id
- companyName
type: ContactEnrich
Enrich Multiple Contacts Using Required Fields and Output Fields for a Full Match.:
summary: Enrich Multiple Contacts Using Required Fields and Output Fields for a Full Match.
description: This example demonstrates how to enrich multiple contacts by using a mix of identifiers—including a combination of firstName, lastName, and companyName, as well as a direct personId. The request specifies a wide range of outputFields, such as email, job title, address, company details, and regulatory flags. This allows for detailed enrichment of each contact. The response returns enriched data for each matched contact, and up to 25 contacts can be processed in a single request.
value:
data:
attributes:
matchPersonInput:
- firstName: henry
companyName: zoominfo
lastName: schuck
- personId: 4191419698
outputFields:
- id
- email
- personHasMoved
- hasCanadianEmail
- region
- jobTitle
- companyName
- companyId
- managementLevel
- companyPrimaryIndustry
- companyEmployeeCount
- street
- city
- region
- metroArea
- zipCode
- state
- country
- directPhoneDoNotCall
- directPhoneAlt
- mobilePhoneAlt
- emailAlt
requiredFields:
- id
- companyName
type: ContactEnrich
Enrich Contact by Person ID Using Output Fields for a No Match:
summary: Enrich Contact by Person ID Using Output Fields for a No Match
description: This example demonstrates how to enrich a single contact using a unique personId. The request specifies a set of outputFields to return, including email, company name, and movement status. The response is a no match response for the contact criteria requested.
value:
data:
attributes:
matchPersonInput:
- personId: 0
outputFields:
- id
- email
- personHasMoved
- hasCanadianEmail
- companyName
type: ContactEnrich
description: The request body containing contact enrich 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/enrich:
post:
operationId: EnrichInterface_enrichCompany
summary: Enrich Companies
description: "The Enrich Companies endpoint can be used to retrieve detailed information about up to 25 individual company records. \nBest practice is to first use [Search Companies](ref:searchinterface_searchcompany) to identify the records \nyou want to enrich, and then use the Company IDs as the input to specify the correct records. If your workflow does not \nsupport a two stage retrieval using both Search and Enrich endpoints, you can query the Company Enrich endpoint with more \nextensive input information and our system will provide the best match available to the input. The more details you provide \nthe more likely we are to provide the correct match. \n\nOnce you have indicated which records you want to enrich, you must then select which fields you want to return for the \nrecords using the `outputFields` list. For more details about all of the available output fields you can select, please \nuse the [Lookup Enrich](ref:lookupenrichinterface_lookupenrich) endpoint (`filter[entity]=company` and `filter[fieldType]=output`). \nThis will provide a description of each available field, as well as whether or not your account has access to this field. \nIf you do not have access to a field that you need, please contact your ZoomInfo Account Manager for purchasing options. \n\nEach record returned by this endpoint will charge a credit from your account, unless that record is already under management \n(see [Credit Usage and Limits Guide](doc:credit-usage-and-limits) for more details). If we fail to find the record and return \n“No match” or if we return an error code a credit will not be charged."
parameters: []
responses:
'200':
description: Success
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/CompanyEnrichResponse'
examples:
Enrich Company Data by Website Using Multiple Output Fields for a Full Match:
summary: Enrich Company Data by Website Using Multiple Output Fields for a Full Match
description: This example demonstrates how to enrich company data using a companyWebsite input and specifying a list of outputFields for the API to return. The response includes the number of matching records. You can include up to 25 company inputs in a single enrich request.
value:
data:
- attributes:
name: ZoomInfo
socialMediaUrls:
- followerCount: '128080'
type: LINKED_IN
url: http://www.linkedin.com/company/zoominfo
- followerCount: '14413'
type: TWITTER
url: http://www.twitter.com/zoominfo
- type: FACEBOOK
url: http://www.facebook.com/109325735758217
ticker: 'NASDAQ: GTM'
website: www.zoominfo.com
id: '344589814'
meta:
input:
companyWebsite: www.zoominfo.com
matchStatus: FULL_MATCH
type: Company
Enrich Company Data Using Multiple Inputs and Output Fields for a Full Match:
summary: Enrich Company Data Using Multiple Inputs and Output Fields for a Full Match
description: This example demonstrates how to enrich multiple companies by providing company details such as companyId and set of outputFields is specified to retrieve detailed company attributes, including website, revenue, social media presence, employee range, parent company details, and more. The response returns enriched data for each matched company. Up to 25 companies can be included in a single enrich request.
value:
data:
- attributes:
certified: true
companyStatus: ALIVE
continent: North America
country: United States
employeeRange: 1,000 - 5,000
foundedYear: '2000'
locationCount: 18
name: ZoomInfo
numberOfContactsInZoomInfo: 4336
parentId: 0
revenue: 245188088
socialMediaUrls:
- followerCount: '128080'
type: LINKED_IN
url: http://www.linkedin.com/company/zoominfo
- followerCount: '14413'
type: TWITTER
url: http://www.twitter.com/zoominfo
- type: FACEBOOK
url: http://www.facebook.com/109325735758217
ticker: 'NASDAQ: GTM'
website: www.zoominfo.com
id: '344589814'
meta:
input:
companyId: 344589814
matchStatus: FULL_MATCH
type: Company
- attributes:
certified: true
companyStatus: ALIVE
continent: North America
country: United States
employeeRange: 50 -100
foundedYear: '2015'
locationCount: 2
name: Comparably
numberOfContactsInZoomInfo: 55
parentId: 344589814
parentName: ZoomInfo Technologies LLC
revenue: 11615
socialMediaUrls:
- followerCount: '19537'
type: TWITTER
url: http://www.twitter.com/comparably
- followerCount: '14413'
type: LINKED_IN
url: http://www.linkedin.com/company/comparably
- followerCount: '6436'
type: FACEBOOK
url: http://www.facebook.com/comparably
website: www.comparably.com
id: '344589814'
meta:
input:
companyId: 344589814
matchStatus: FULL_MATCH
type: Company
Enrich Company Data by Website Using Multiple Output Fields resulting no Match:
summary: Enrich Company Data by Website Using Multiple Output Fields resulting no Match
description: This example demonstrates how to enrich company data using a companyWebsite input and specifying a list of outputFields for the API to return. The response is a no match response for the company criteria requested.
value:
data:
- id: '0'
meta:
input:
companyWebsite: www.no-company.com
matchStatus: NO_MATCH
type: NoMatch
'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:
- Enrich
requestBody:
required: true
content:
application/vnd.api+json:
schema:
$ref: '#/components/schemas/CompanyEnrichRequest'
examples:
Enrich Company Data by Website Using Multiple Output Fields for a Full Match:
summary: Enrich Company Data by Website Using Multiple Output Fields for a Full Match
description: This example demonstrates how to enrich company data using a companyWebsite input and specifying a list of outputFields for the API to return. The response includes the number of matching records. You can include up to 25 company inputs in a single enrich request.
value:
data:
attributes:
matchCompanyInput:
- companyWebsite: www.zoominfo.com
outputFields:
- id
- ticker
- name
- website
- socialMediaUrls
type: CompanyEnrich
Enrich Company Data Using Multiple Inputs and Output Fields for a Full Match:
summary: Enrich Company Data Using Multiple Inputs and Output Fields for a Full Match
description: This example demonstrates how to enrich multiple companies by providing company details such as companyId and set of outputFields is specified to retrieve detailed company attributes, including website, revenue, social media presence, employee range, parent company details, and more. The response returns enriched data for each matched company. Up to 25 companies can be included in a single enrich request.
value:
data:
attributes:
matchCompanyInput:
- companyId: 344589814
- companyId: 344589814
outputFields:
- id
- ticker
- name
- website
- socialMediaUrls
- revenue
- numberOfContactsInZoomInfo
- country
- continent
- companyStatus
- alexaRank
- hashtags
- certified
- employeeRange
- employeeRange
- employeeGrowth
- parentId
- parentName
- locationCount
- foundedYear
type: CompanyEnrich
Enrich Company Data by Website Using Mu
# --- truncated at 32 KB (170 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/zoominfo/refs/heads/main/openapi/zoominfo-enrich-api-openapi.yml