ZenZap Long Polling API
Long polling allows your integration to fetch outbound events instead of receiving webhooks.Use `GET /v2/updates` with:- `offset`: value returned as `nextOffset` from the previous response- `limit`: max updates per request (default 50, max 100)- `timeout`: wait time in seconds when no updates are available (default 0, max 30)Event payloads in polling responses match webhook `data` payloads for the same event type.This includes `data.message.attachments[]` with signed URLs for file/image/video/audio messages.
ZenZap Long Polling API is one of 8 APIs that ZenZap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Long Polling. 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 16 schemas. It is described by OpenAPI 3.0.3, 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 Long Polling 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 GET. Each is listed below with its method, path, parameters, and response codes.
Long polling allows your integration to fetch outbound events instead of receiving webhooks. Use GET /v2/updates with: - offset: value returned as nextOffset from the previous res…
Schemas 16
The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are WebhookMessage (17 properties), WebhookTask (10 properties), WebhookReactionData (7 properties), WebhookContact (7 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.