Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ZoomInfo Authentication API

The ZoomInfo API authenticates client access requests using a JSON Web Token (JWT). A JWT is a string that is generated by the server for the client that can then be passed along in an HTTPS request.**Note**: The Authenticate endpoint is one method for authenticating with the ZoomInfo API with a username and password. For other methods that utilize public libraries for Java, Python, and NodeJS, see the 'Authentication methods' section in the [ZoomInfo API introduction](#intro).To obtain the token, the client exchanges valid user credentials with the server which generates the token and provides it back to the client. An access token generally has a set expiration time after which a new token will need to be requested by the client.Use the Authenticate endpoint to pass valid ZoomInfo user credentials to the API. If authentication is successful, a JWT access token is provided in the response body.**Important: The token is good for 60 minutes from the time that the response was generated.*** **Do not generate a new JWT with every call/request.*** **As a best practice to keep the session active, refresh the JWT every 55 minutes.**

ZoomInfo Authentication API is one of 23 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 Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 168 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 1.0.

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

1 operations 1 paths 1 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Server
https://api.zoominfo.com
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

ZoomInfo Authentication 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 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Authentication 1

The ZoomInfo API authenticates client access requests using a JSON Web Token (JWT). A JWT is a string that is generated by the server for the client that can then be passed along…

POST
/authenticate
Zoominfo Authenticate
Authenticate body → default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is AuthenticateRequest (2 properties). Each schema is shown below with its type and property counts.

AuthenticateRequest
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoominfo-authentication-api-openapi.yml Raw ↑

Other APIs ZoomInfo publishes across the network.

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 Contact Search API
ZoomInfo Corporate Hierarchy Enrich API
ZoomInfo Hashtags Enrich API
ZoomInfo Intent Enrich API
ZoomInfo Intent Search API