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 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 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.2.0, at version 1.0.
Requests are made against a single base URL, https://api.zoominfo.com.
Metadata
The identity and technical contract details declared by the specification.
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.
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…
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.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from ZoomInfo 12
Other APIs ZoomInfo publishes across the network.
This is an independent, third-party profile of ZoomInfo Authentication 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.