How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zoca Comms Inbox API

The Comms Inbox API from Zoca — 10 operation(s) for comms inbox.

Zoca Comms Inbox API is one of 193 APIs that Zoca publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Comms Inbox. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 10 paths. It is described by OpenAPI 3.2.0, at version 3.20.10.

Requests are made against a single base URL, https://api.zoca.ai.

10 operations 10 paths 0 schemas 7 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.20.10
Base URL
https://api.zoca.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Zoca Comms Inbox API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (access-token).

  • access-token — Enter JWT token in the format Bearer

Paths & Operations 10

Across 10 paths, the API surfaces 10 operations — 7 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Comms Inbox 10
GET
/comms-inbox/multilocation/{businessEntityId}
List inbox conversations across managed business locations
t_value → 200
GET
/comms-inbox/multilocation/{businessEntityId}/location/{entityId}/client/{clientId}
Get a managed location conversation timeline
t_value → 200
POST
/comms-inbox/multilocation/{businessEntityId}/location/{entityId}/client/{clientId}/close
Close a conversation at a managed business location
t_value → 201
GET
/comms-inbox/ops/entities
Search active FrontDesk locations for operations
t_value 3 params → 200
GET
/comms-inbox/ops
List conversations across active FrontDesk entities
t_value 3 params → 200
GET
/comms-inbox/entity/{entityId}
List inbox conversations for an entity
t_value 7 params → 200
GET
/comms-inbox/entity/{entityId}/client/{clientId}
Get the SMS + call timeline for one client
t_value → 200
GET
/comms-inbox/entity/{entityId}/unread-count
Get the durable unread Inbox SMS count for an entity
t_value → 200
POST
/comms-inbox/entity/{entityId}/client/{clientId}/read
Mark an Inbox conversation read through a rendered inbound message
t_value → 201
POST
/comms-inbox/entity/{entityId}/client/{clientId}/close
Manually close a conversation with a staff-set disposition
t_value → 201

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoca-comms-inbox-api-openapi.yml Raw ↑

Other APIs Zoca publishes across the network.

Zoca ACM API
Zoca Acuity API
Zoca Addon Groups API
Zoca Addons API
Zoca Aeo Lead Magnet API
Zoca Agents API
Zoca API Keys API
Zoca App API
Zoca App Blocker API
Zoca App Blocker Updates API
Zoca Approvals API
Zoca Auth API
Where this information came from

This is an independent, third-party profile of Zoca Comms Inbox 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.