ZenZap Polls API
Operations for creating polls, recording votes, and retracting votes.Polls are posted as messages in a topic. When you create a poll, each option is assigned a server-generated 6-character ID — use those IDs as `optionId` when submitting votes.**Voting constraints:**- The bot must be a member of the topic the poll was posted in- Anonymous polls (`anonymous: true`) do not support voting via the API- Votes cannot be cast on closed or expired polls- Each `{pollId, optionId, voter}` combination is idempotent- Votes can be retracted with `DELETE /v2/polls/{pollId}/votes/{voteId}` using the `id` returned when the vote was cast
ZenZap Polls API is one of 8 APIs that ZenZap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Polls. The published artifact set on APIs.io includes an OpenAPI specification and rate-limit docs.
This API exposes 3 operations across 3 paths, and defines 5 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 Polls 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 3
Across 3 paths, the API surfaces 3 operations — 1 DELETE, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Operations for creating polls, recording votes, and retracting votes. Polls are posted as messages in a topic. When you create a poll, each option is assigned a server-generated 6…
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PollCreateResponse (8 properties), PollCreateRequest (5 properties), PollVoteCreateResponse (4 properties), PollOption (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.