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

ZenZap Messages API

Operations for sending messages

ZenZap Messages API is one of 8 APIs that ZenZap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Messages. The published artifact set on APIs.io includes an OpenAPI specification and rate-limit docs.

This API exposes 7 operations across 6 paths, and defines 7 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.

7 operations 6 paths 7 schemas 2 DELETE1 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0.0
Base URL
https://api.zenzap.co
Authentication
HTTP Bearer, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 3

ZenZap Messages 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 7

Across 6 paths, the API surfaces 7 operations — 2 DELETE, 1 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Messages 7

Operations for sending messages

POST
/v2/messages
Send a message
createMessage 2 params body → 200201400401500
DELETE
/v2/messages/{messageId}
Delete a message
deleteMessage 3 params → 204400401403404500
PATCH
/v2/messages/{messageId}
Edit a message
patchMessage 3 params body → 200400401403404500
POST
/v2/messages/{messageId}/reactions
Add a reaction to a message
addMessageReaction 3 params body → 200201400401403404500
DELETE
/v2/messages/{messageId}/reactions/{reactionId}
Remove a reaction from a message
deleteMessageReaction 4 params → 204400401403404500
POST
/v2/messages/{messageId}/delivered
Mark a message as delivered
markMessageDelivered 3 params → 200400401500
POST
/v2/messages/{messageId}/read
Mark a message as read
markMessageRead 3 params → 200400401500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are MessageReactionCreateResponse (4 properties), MessageFileMetaRequest (4 properties), MessageCreateResponse (3 properties), MessageCreateRequest (3 properties). Each schema is shown below with its type and property counts.

MessageFileMetaRequest
object
4 properties 1 required
MessageReactionCreateResponse
object
4 properties
MessageReactionCreateRequest
object
1 property 1 required
MessagePatchRequest
object
1 property 1 required
MessageCreateRequest
object
3 properties 2 required
MessageFileUploadRequest
object
2 properties 2 required
MessageCreateResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zenzap-messages-api-openapi.yml Raw ↑

Other APIs ZenZap publishes across the network.

ZenZap Agentic API
ZenZap Long Polling API
ZenZap Members API
ZenZap OAuth API
ZenZap Polls API
ZenZap Tasks API
ZenZap Topics (group chats/channels/conversations) API