Skip to main content
Telara

Integrations / Vapi

Vapi logo

Vapi

Vapi voice agents — POST /analytics (apis.io). Bearer private key.

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 Vapi organization you can administer.
Org admin who can open the dashboard API keys page.

Vendor setup

Get the credential

1
Open API Keys
Sign in to the Vapi dashboard. Open Organization → API Keys (or the sidebar API Keys item).
2
Create a key
Click Create API Key. Name it for Telara. Copy the bearer token immediately. Prefer a private/org key over a public key.
3
Paste in Telara
Settings → Integrations → Vapi. Paste the private key into the field Telara shows.

In Telara

Connect in Telara

API key

API bearer token from the vendor dashboard.

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

Fields Telara asks for
  • API key

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.

  • calls
    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

Public keys are for client SDKs. Telara needs the private org key that can read usage.
A key on the wrong org lists the wrong call minutes.