How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ZoomInfo Contact Search API

Use [Contact Search](#2e5121fd-df42-41a4-95d6-0e8f24eebd92) to retrieve contacts using valid query parameters.* To build your request, retrieve a list of valid query parameters using [Contact Search Inputs](#74630827-dd25-4b6a-bf72-f7cfeffd6c41).* For requests that require you to specify supported values (e.g., job titles, industry codes and so on), use the [Lookup](#efe7b4b8-1ef2-4fcd-a20f-9da68f6b2055) endpoints.* Use [Contact Search Outputs](#5ed629a9-f24a-41a3-bc66-89f3f09f051c) to retrieve a list of expected response fields that will be returned from [Contact Search](#2e5121fd-df42-41a4-95d6-0e8f24eebd92).

ZoomInfo Contact Search API is one of 42 APIs that ZoomInfo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 168 JSON Schema definitions.

Tagged areas include Contact Search. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 168 JSON Schemas.

This API exposes 3 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.zoominfo.com.

3 operations 3 paths 6 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.zoominfo.com
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

ZoomInfo Contact Search API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (httpBearer). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT token obtained from the /authenticate endpoint

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Contact Search 3

Use [Contact Search](2e5121fd-df42-41a4-95d6-0e8f24eebd92) to retrieve contacts using valid query parameters. To build your request, retrieve a list of valid query parameters usin…

POST
/search/contact
Zoominfo Contact Search
ContactSearch body → 200
GET
/lookup/inputfields/contact/search
Zoominfo Contact Search Inputs
ContactSearchInputs → 200
GET
/lookup/outputfields/contact/search
Zoominfo Contact Search Outputs
ContactSearchOutputs → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Datum (21 properties), ContactSearchRequest (7 properties), ContactSearchInput (4 properties), SearchcontactsbyZipCoderadius (4 properties). Each schema is shown below with its type and property counts.

ContactSearchRequest
object
7 properties 7 required
Datum
object
21 properties 21 required
SearchcontactsbyZipCoderadius
object
4 properties 4 required
Company
object
2 properties 2 required
ContactSearchInput
object
4 properties 4 required
ContactSearchOutput
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoominfo-contact-search-api-openapi.yml Raw ↑

Other APIs ZoomInfo publishes across the network.

ZoomInfo Authentication API
ZoomInfo Bulk API
ZoomInfo Company Enrich API
ZoomInfo Company Location Enrich API
ZoomInfo Company Master Data Enrich API
ZoomInfo Company Search API
ZoomInfo Compliance API API
ZoomInfo Contact Enrich API
ZoomInfo Corporate Hierarchy Enrich API
ZoomInfo Hashtags Enrich API
ZoomInfo Intent Enrich API
ZoomInfo Intent Search API
Where this information came from

This is an independent, third-party profile of ZoomInfo Contact Search API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.