Chorus API

Name: Chorus API
Brand: Chorus API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer SuccessapiKey4 EndpointsREST

For Agents

Retrieve sales call recordings, transcripts, and conversation insights from Chorus.ai for revenue intelligence and coaching workflows.

Install Jentic One Beta

Connect the Chorus API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chorus API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Chorus API.

List recorded sales calls with metadata via /calls

Retrieve a specific call by ID through /calls/{callId} with participant and recording detail

Pull a full call transcript with speaker labels and timestamps from /transcripts/{callId}

GET STARTED

Start building with Chorus API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Chorus API, keeping it validated and agent-ready. Chorus.ai is a conversation intelligence platform owned by ZoomInfo that records, transcribes, and analyses sales calls and customer meetings. The API exposes call records, full transcripts, and AI-generated insights — themes, objections, talk-time ratios, and competitor mentions — so revenue teams can pipe call data into CRMs, coaching tools, and analytics dashboards. The endpoints are read-only and authenticated via an API key in the Authorization header.

Use Cases

Patterns agents use Chorus API for, with concrete tasks.

★ CRM Call Logging Integration

Sync recorded sales calls and their transcripts back into the CRM so reps and managers can see conversation history alongside the deal record. The /calls and /transcripts/{callId} endpoints provide the raw data; an integration job reads new calls, attaches transcripts to the related opportunity, and writes a summary note. This is the standard pattern for closing the loop between conversation intelligence and pipeline data.

List calls from /calls in the last 24 hours, fetch each transcript via /transcripts/{callId}, and post the summary to the related CRM opportunity

Sales Coaching and Review

Sales managers identify coaching moments by pulling transcripts of specific calls and reviewing how reps handled objections, pricing questions, or competitor mentions. The /insights endpoint surfaces these moments programmatically — themes, talk-time ratios, and mentioned topics — so a coaching app can highlight calls that need review without a manager listening end-to-end.

Fetch /insights for the last 7 days and surface calls where competitor mentions exceed 3 occurrences

Revenue Intelligence Reporting

Revenue operations teams build dashboards that aggregate call activity — number of calls per rep, average duration, themes discussed — into weekly performance reports. The /calls endpoint provides the activity feed and /insights provides the qualitative layer. This lets RevOps measure conversation patterns alongside pipeline velocity in one view.

Aggregate /calls counts and /insights themes by rep for the last week and emit a weekly RevOps summary

Agent-Driven Deal Briefing

An AI agent preparing a sales rep for an upcoming call calls Chorus through Jentic to summarise prior conversations with the same account. The agent searches Jentic for 'get sales call transcript', loads the transcripts operation, and pulls the last few calls so it can produce a concise pre-call briefing without the rep manually scrubbing through Chorus.

Search Jentic for 'get sales call transcript', load /transcripts/{callId}, and summarise the last three calls for an account into a briefing

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for chorus api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/calls

List recorded calls

GET

/calls/{callId}

Get a specific call

GET

/transcripts/{callId}

Get the transcript for a call

GET

/insights

Get conversation insights

GET

/calls

List recorded calls

GET

/calls/{callId}

Get a specific call

GET

/transcripts/{callId}

Get the transcript for a call

GET

/insights

Get conversation insights

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Chorus API keys are stored encrypted in the Jentic vault. Agents receive scoped access — the raw token never enters the agent's context or appears in logs.

Intent-based discovery

Agents search by intent (e.g., 'get sales call transcript') and Jentic returns the matching Chorus operation along with its parameter schema.

Time to first call

Direct integration: 1-2 days for auth, pagination, and transcript handling. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Chorus API through Jentic.

Why is there no official OpenAPI spec for Chorus API?

Chorus.ai does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Chorus API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Chorus API use?

Chorus uses an API key passed in the Authorization header on each request. Through Jentic, the key is stored encrypted in the vault and never enters the agent's context — the agent receives a scoped reference rather than the raw token.

Can I get call transcripts from Chorus through the API?

Yes. The /transcripts/{callId} endpoint returns the full speaker-labelled transcript for a given call ID, including timestamps, which you can use for downstream summarisation, coaching, or CRM logging.

What conversation insights are available?

The /insights endpoint surfaces machine-derived signals from Chorus's conversation analysis — themes discussed, objections raised, competitor mentions, talk-time ratios, and other call-level metrics that can be used to prioritise coaching and reporting.

What are the rate limits for the Chorus API?

Specific limits are not declared in the OpenAPI spec. Chorus enforces request throttling at the account level; honour the standard 429 backoff pattern and check your account dashboard for current quotas.

How do I get a call transcript through Jentic?

Run pip install jentic, search for 'get sales call transcript', load the /transcripts/{callId} operation, and execute with the call ID. Jentic injects the Authorization header from the vault and returns the parsed transcript.