ZenZap O Auth API
OAuth 2.0 `client_credentials` grant. Used by API-key bots that were created with `credentialType: oauth` to mint short-lived bearer access tokens.**In a nutshell:**1. Get a `clientId` and `clientSecret` from your bot in the Zenzap admin console. The `clientSecret` is shown once at creation; if lost, rotate it from the same screen.2. `POST /oauth/token` with `grant_type=client_credentials` to receive a JWT access token (1-hour TTL).3. Call any `/v2/*` endpoint with `Authorization: Bearer `. No `X-Signature` / `X-Timestamp` headers are needed on the OAuth path.4. Re-mint when the token expires. There is **no refresh token**.Scopes are granular per endpoint — see the [Authentication page](/api-reference/authentication#oauth-scopes) for the full scope catalog and the endpoint → scope mapping.
ZenZap O Auth API is one of 8 APIs that ZenZap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification and rate-limit docs.
This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.
Requests are made against a single base URL, https://api.zenzap.co.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
ZenZap O Auth API declares
3 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
An API key is passed in the header as X-Signature (hmacSignature).
It supports OAuth 2.0 (oauth2ClientCredentials) using the clientCredentials flow, exposing 12 scopes.
By default, every request must be authenticated.
bearerAuth— Bearer token for the request. Two flavors: - Static API key — pass your API key (the value returned as apiKey when the bot was created). Must be paired with X-…hmacSignature— HMAC-SHA256 signature for request verification. Required only when authenticating with a static API key. Omit when using an OAuth access token.oauth2ClientCredentials— OAuth 2.0 clientcredentials grant for API-key bots. Use the clientId and clientSecret returned when the bot was created (or rotated) to mint short-lived access…
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.
OAuth 2.0 clientcredentials grant.
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are OAuthTokenResponse (4 properties), OAuthTokenRequest (4 properties), OAuthErrorResponse (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 ZenZap 7
Other APIs ZenZap publishes across the network.
This is an independent, third-party profile of ZenZap O Auth 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.