--- title: Chorus API Integration on Truto slug: chorus category: Conversational Intelligence canonical: "https://truto.one/integrations/detail/chorus/" --- # Chorus API Integration on Truto **Category:** Conversational Intelligence **Status:** Generally available ## Unified APIs ### Unified Conversational Intelligence API - **Meetings** — The meeting represent a meeting in the conversation. - **Users** — The user represent a user in the conversation. ## How it works 1. **Link your customer's Chorus account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Chorus.** The Proxy API is a 1-to-1 mapping of the Chorus API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Enrich deal forecasting with conversation signals** — RevOps and forecasting platforms can pull Chorus meeting data — including AI-detected topics, competitor mentions, and transcript snippets — to generate deal health scores that go beyond CRM stage data alone. - **Build a unified coaching library from recorded calls** — Sales enablement and LMS platforms can ingest Chorus meetings, recordings, and transcripts to let managers curate training playlists and deliver timestamped coaching feedback inside their own product. - **Surface voice-of-customer insights for product teams** — Product management and feedback aggregation tools can scan Chorus transcripts for feature requests, bug mentions, and sentiment signals, turning raw call data into actionable engineering tickets without relying on sales reps to relay information. - **Sync call activity into niche or vertical CRMs** — Industry-specific CRMs that aren't natively supported by Chorus can use Truto to pull meeting metadata, attendees, and transcripts, matching participants to their own contact records so users never leave their primary workflow. - **Trigger real-time workflows from meeting events** — Workflow automation and collaboration platforms can monitor Chorus meetings for specific topics or keywords and route alerts, summaries, or follow-up tasks into tools like Slack, Jira, or internal dashboards. ## What you can build - **Automatic call log sync to CRM contacts** — Match Chorus meeting attendees by email to your app's contact records and auto-attach transcripts, AI summaries, and recording links to the right account or opportunity. - **AI deal risk detection from conversation topics** — Ingest the topics and transcript data from Chorus meetings to flag deals where pricing objections, competitor mentions, or stalled next steps appear repeatedly. - **Embedded call playback with searchable transcripts** — Surface Chorus audio and video recording URLs alongside timestamped, speaker-attributed transcripts directly inside your product's UI for in-context review. - **User-aware data scoping via Chorus user mapping** — Pull Chorus user profiles to map call owners to your app's user accounts, enforcing correct data visibility and permission boundaries across teams. - **Keyword-triggered VOC snippet extraction** — Scan meeting transcripts for configurable keywords like 'bug,' 'integration,' or competitor names and automatically clip the relevant timestamped passage into a structured insight feed. - **Team-level conversation analytics dashboard** — Aggregate meeting durations, talk-to-listen ratios, and topic frequency across all Chorus users to give managers a single pane of glass for coaching metrics. ## FAQs ### How does authentication work for the Chorus integration? Chorus uses token-based authentication via its REST API. Your end users provide their API token through Truto's managed auth flow, so you never have to handle credential storage or renewal directly. ### What data can I access through the Unified Conversational Intelligence API for Chorus? The Unified API exposes Meetings and Users. Meetings include metadata (title, duration, timestamps), attendees, audio/video recording URLs, AI-detected topics, and timestamped speaker-attributed transcripts. Users include profile details like email, name, and role. ### Are there specific Truto tools available for Chorus today? No pre-built tools are available for Chorus at this time. They are built on request — reach out to the Truto team with your use case and they will scope and deliver the tooling you need. ### Does Truto handle pagination and rate limits for the Chorus API? Yes. Truto abstracts away pagination logic and respects Chorus's rate limits automatically, so your application receives complete result sets without needing to manage cursors or back-off strategies. ### Can I map Chorus meeting attendees to contacts in my own application? Yes. Each meeting's attendees array includes email addresses and host indicators. You can match these against your own user or contact records to attribute call activity to the correct accounts. ### How fresh is the data when I query Chorus through Truto? Truto queries the Chorus API in real time (or near-real-time with proxy requests), so data freshness matches what the Chorus API itself provides. Transcripts and AI analysis are available once Chorus has finished processing a recording.