Skip to content
Last updated

Chorus integration

Chorus (by ZoomInfo) is a conversation intelligence platform that records, transcribes, and analyzes sales calls, meetings, and emails to surface deal and coaching insights. Integrating Chorus with Frontegg allows your application to access engagements, calls, transcripts, and related revenue data on behalf of your users using a personal API token.

Chorus does not offer OAuth 2.0 — the integration authenticates with a personal API token that is sent in the Authorization header of each request.


Prerequisites

  • A Chorus account whose role is permitted to access the Chorus API (enabled by an admin under Roles & permissions)
  • Admin access to Roles & permissions if API access is not yet enabled for your role

Connect Chorus

Step 1: Enable API access for your role

API tokens can only be created by users whose Chorus role allows API access. If your role does not yet have it, ask a Chorus admin to enable API access for your role under Roles & permissions settings.

Step 2: Open your personal settings

Sign in to Chorus and open your Personal Settings page, where API tokens are managed.

Step 3: Generate an API token

On the Personal Settings page, generate a personal API token. Give it a descriptive name so you can identify it later.

Early access

Chorus API access is offered as an early-access program. If you do not see the option to generate a token, contact your Chorus customer success manager to have a personal API token issued for your account.

Step 4: Copy the API token

Copy the generated token and store it securely — you will need it to configure the integration in the Frontegg portal. If the token is shown only once, copy it before leaving the page.

Configure the Frontegg portal

Once you have your API token, configure the integration in the Frontegg portal:

  1. Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Chorus.
  2. Enter your API token in the API Key field.
  3. Click Save.

Keep your credentials secure

Never share or commit your API token to version control. The token grants access according to your Chorus role, so treat it with the same care as your password.

Additional resources