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

Chorus.ai Conversations API

The Conversations API from Chorus.ai — 11 operation(s) for conversations.

Chorus.ai Conversations API is one of 22 APIs that Chorus.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conversations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 13 operations across 11 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 26.33.08.

Requests are made against 2 base URLs: /, https://chorus.ai.

13 operations 11 paths 13 schemas 3 DELETE4 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
26.33.08
Base URL
https://chorus.ai/api/v1
Authentication
HTTP Basic, HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

Chorus.ai Conversations API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basic). It accepts HTTP bearer tokens (bearer-token). An API key is passed in the header as x-ziaccesstoken (x-ziaccesstoken). By default, every request must be authenticated.

  • basic — HTTP basic authentication (for those APIs that support it).
  • bearer-token — A Chorus token or a signed JWT.
  • x-ziaccesstoken — A ZoomInfo access token.

Paths & Operations 13

Across 11 paths, the API surfaces 13 operations — 3 DELETE, 4 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Conversations 13
GET
/api/v1/conversations/live
Fetch a LIVE conversation using meeting uuid or user id
get-api-v1-conversations-live 3 params → 200400404
DELETE
/api/v1/conversations/{id}
Delete a conversation record
delete-api-v1-conversations-id 2 params → 202400404
GET
/api/v1/conversations/{id}
Fetch a specific conversation
get-api-v1-conversations-id 7 params → 200400404
POST
/api/v1/conversations/{id}/actions/disconnect
Disconnect a live conversation
post-api-v1-conversations-id-actions-disconnect 1 param body → 204400409
GET
/api/v1/conversations/{id}/media
Download media file or metadata
get-api-v1-conversations-id-media 2 params → 200400404
POST
/api/v1/conversations:bulk
Bulk process conversations
post-api-v1-conversations:bulk body → 202400409
POST
/api/v1/conversations:export
Export recordings
post-conversations-export body → 202
POST
/api/v1/conversations:validate
Create a new conversations:validate$
post-api-v1-conversations:validate body → 201400409
POST
/api/v1/join
Join a live call
post-api-v1-join body → 201400409
DELETE
/v3/engagements
Delete multiple engagements
delete-v3-engagements 1 param → 202
GET
/v3/engagements
Get conversations
get-v3-engagements 18 params → 200
DELETE
/v3/engagements/{engagement_id}
Delete a single engagement
delete-v3-engagements-id 1 param → 202
POST
/v3/upload
Upload a conversation
post-v3-upload body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are MeetingValidation (7 properties), BulkProcessConversationsRequest (3 properties), MeetingAutojoin (3 properties), Conversation (3 properties). Each schema is shown below with its type and property counts.

AnyValue
Can be any value.
Task
object
3 properties 3 required
Conversation
object
3 properties 3 required
MeetingAutojoinDoc
object
1 property 1 required
Error
object
1 property 1 required
MeetingValidation
object
7 properties 5 required
BulkProcessConversationsResponse
object
2 properties
ConversationDoc
object
1 property 1 required
RecordingDoc
object
1 property 1 required
MeetingAutojoin
object
3 properties 3 required
BulkProcessConversationsRequest
object
3 properties
Recording
object
3 properties 3 required
TaskDoc
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chorus-ai-conversations-api-openapi.yml Raw ↑

Other APIs Chorus.ai publishes across the network.

Chorus.ai Auth API
Chorus.ai Emails API
Chorus.ai Engagement filter API
Chorus.ai Event API
Chorus.ai External Moments API
Chorus.ai Integrations Calendar API
Chorus.ai Integrations CRM API
Chorus.ai Integrations Email API
Chorus.ai Integrations Meet API
Chorus.ai Playlists API
Chorus.ai Public External Moments API
Chorus.ai Public Playlist Moments API
Where this information came from

This is an independent, third-party profile of Chorus.ai Conversations 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.