> ## Documentation Index
> Fetch the complete documentation index at: https://support.configview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deepgram setup

ConfigView reads your Deepgram (speech AI) account through the Deepgram **Management API** (`https://api.deepgram.com/v1`), using an **API key** that a Deepgram admin creates. ConfigView sends only `GET` requests. It never creates, changes or deletes anything in Deepgram.

You will end up with **1 required secret** (`DEEPGRAM_API_KEY`) and **1 optional secret** (`DEEPGRAM_API_BASE`, only for EU, Australia or India accounts) in ConfigView when setup is complete.

> **Scope of this integration today.** ConfigView reads who has access to Deepgram and who is spending on it: your projects, the members of each project with their role and scopes, pending invites, API key metadata (name, scopes, created date, owner), daily usage per API key and per model for the last 30 days, and credit balances. It does **not** read transcripts, audio, request contents or API key secrets.

***

## What you need

* A Deepgram **Owner** or **Admin** on each project you want covered
* A key with enough reach to see every member and key. A key with the plain **Member** role sees only the keys it created.

***

## Step 1: Open the Deepgram page in ConfigView

Open ConfigView in a second browser tab and leave it open:

`https://{companyname}.configview.com/admin/integrations/deepgram`

***

## Step 2: Create the API key

1. In the [Deepgram Console](https://console.deepgram.com) open a project and go to **Settings > API Keys > Create a New API Key**
2. Name it (for example `ConfigView`) and set an expiration date you are comfortable renewing
3. Choose the least access that still works:
   * the **Admin** role (or **Owner**) is the simplest, or
   * a custom scope list limited to the read permissions: `project:read`, `keys:read`, `members:read`, `members:read:invites`, `members:read:scopes`, `usage:read` and `billing:read`
4. Copy the key now. Deepgram shows it once.
5. In the ConfigView tab paste it into `DEEPGRAM_API_KEY` under **Credentials** and save

A key can only grant permissions its creator has. ConfigView reads every project the key can see; if you want several projects covered, create the key as a person who belongs to all of them.

**Other regions.** If your account is on the EU, Australia or India endpoint, also set `DEEPGRAM_API_BASE` to `https://api.eu.deepgram.com/v1`, `https://api.au.deepgram.com/v1` or `https://api.in.deepgram.com/v1`. Leave it empty for the default.

***

## Step 3: Connect and verify

1. Click **Connect**. ConfigView creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Projects** | The projects the key can see. Every other script runs once per project. |
| **Members** | Everyone with access to a project: work email, name, role and scopes. |
| **Invites** | Pending invitations and the role they were sent with. |
| **API keys** | Key name, scopes, created date and owner. Never the secret. |
| **Usage by API key** | Daily requests, audio hours, tokens and text-to-speech characters per key. |
| **Usage by model** | The same measures per model. |
| **Balances** | Outstanding credit balance per project. |

2. Click **Verify now**. The health check reads the secret, then lists the projects and the members of the first one.

If a check fails:

* **401.** The key is wrong, revoked or expired, or your account lives in another region (set `DEEPGRAM_API_BASE`).
* **403.** The key lacks a permission, for example `members:read` or `billing:read`. That area is skipped; the rest still collects.

***

## Data Tables

Each table has a `run_at` column and keeps only the newest run. Every table except `deepgram_projects` also carries `project_id` and `project_name`.

| Table | Source | Key Columns |
| - | - | - |
| `deepgram_projects` | `GET /projects` | project\_id, name |
| `deepgram_members` | `GET /projects/{id}/members` | member\_id, email, first\_name, last\_name, member\_role, scopes |
| `deepgram_invites` | `GET /projects/{id}/invites` | email, scope |
| `deepgram_keys` | `GET /projects/{id}/keys` | api\_key\_id, comment, scopes, created\_at, owner\_member\_id, owner\_email |
| `deepgram_usage_by_key` | `GET /projects/{id}/usage/breakdown?grouping=accessor` | accessor (the key id), period\_start, requests, audio\_hours, tokens\_in, tokens\_out, tts\_characters |
| `deepgram_usage_by_model` | `GET /projects/{id}/usage/breakdown?grouping=models` | models, period\_start, requests, audio\_hours, tokens\_in, tokens\_out, tts\_characters |
| `deepgram_balances` | `GET /projects/{id}/balances` | balance\_id, amount, units, purchase\_order\_id |

***

## Things worth knowing

**No last-used or expiry for keys.** Deepgram's key list returns no last-used time and no expiration date. ConfigView derives "unused" from usage: a key with no requests in the last 30 days.

**Departed owners.** A key keeps working after its creator leaves the project. ConfigView flags keys whose owner is no longer a member.

**People in several projects.** Access is per project, so someone in three projects appears three times in the members table.

**Usage is by key id.** The usage breakdown names an API key by its id (`accessor`). Join it to the API keys table to see the key name and owner. Model values are reported as Deepgram returns them.

**Rate limit.** Deepgram limits concurrent requests per project and documents nothing for the Management endpoints. ConfigView calls one endpoint at a time, paces itself at 60 requests a minute, waits as long as Deepgram asks on a 429, and the Management API has no pagination.

## What isn't collected

* Transcripts, audio and any request or response content
* API key values
* Project company or billing contact details, and individual billing transactions


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.