Skip to main content
Telara

Integrations / Deepgram

Deepgram logo

Deepgram

Deepgram GET /v1/projects/{project_id}/usage. Speech spend connector.

API key
Spend

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions NoReal-time events No

Before you connect

Prerequisites

A Deepgram project you can administer.
Project admin who can create API keys.

Vendor setup

Get the credential

1
Open API keys
Sign in to the Deepgram console. Open the project → Settings → API Keys.
2
Create a key
Click Create a New API Key. Name it for Telara. Copy the key once. Also copy the Project ID from Settings → General.
3
Paste in Telara
Settings → Integrations → Deepgram. Paste the API key and the project id.

In Telara

Connect in Telara

API key

Deepgram API key (Bearer) plus project_id.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key
  • Project Id

Spend

What gets measured

Resolution: Aggregated buckets.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • hours
    count
  • requests
    count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

A key on the wrong project lists the wrong usage.
Member keys that cannot read usage connect and then show zeros.