Skip to main content
Configview reads which meetings tl;dv has recorded through tl;dv’s public API, using one API key. You create it in tl;dv. You will end up with 1 required secret (TLDV_API_KEY) in Configview when setup is complete.
Scope of this integration today. Configview reads meeting metadata for the account that owns the key: who organized each meeting, when, how long it ran, how many people were invited and how many of them are outside the organizer’s company, plus the folder names and how many meetings each holds. It never collects meeting titles, links, recordings, transcripts, notes, highlights or invitee names and addresses. Configview only reads. It never imports, uploads or deletes anything.

Plan requirements

The tl;dv API is available on Pro, Business and Enterprise plans. The Free plan has no API access, so the health check fails on Free.

Step 1: Open the tl;dv page in Configview

https://{companyname}.configview.com/admin/integrations/tldv

Step 2: Create an API key

  1. In tl;dv open Settings, then Integrations, then API
  2. Create a new key and copy it
  3. Paste it into TLDV_API_KEY under Credentials in Configview and click the save icon

What the key can see

tl;dv API keys are personal. A key sees the meetings of the user who created it (meetings belong to the calendar organizer, and the key can also see meetings shared with that user). It does not see the rest of the company. To inventory a team, use the account of the person or the shared recorder account whose meetings you want covered. tl;dv has no read-only key scope; Configview only sends GET requests. If that person leaves, the key stops working. Create a new key from a current account and paste it again.

Step 3: Connect and verify

  1. Confirm the credential shows as saved, then click Connect. Configview creates its tables and schedules each collector at your default run time
  2. Click Verify now. The health check confirms the key is not empty and reads one meeting row
If a check fails:
  • 401 or 403. The key was revoked, mistyped, or the plan has no API access.
  • 403 with a short message. tl;dv rejects clients without their own User-Agent. Configview sends one; a proxy that strips it causes this.

Data Tables

Each includes a run_at column. Both tables keep only the newest run.

Things worth knowing

External means a different email domain. An invitee counts as external when their email domain differs from the organizer’s. A customer with the same domain as a partner company still counts once per person; the domain count shows how many different outside companies were on the call. Lookback. Configview reads the last 90 days of meetings. tl;dv caps a query at 10,000 results, so a long window on a very busy account could be cut off. Rate limit. tl;dv documents no request limit for read endpoints. Configview paces itself at 30 requests a minute and waits when tl;dv answers 429. API is alpha. The endpoints are versioned v1alpha1 and tl;dv warns they may change.

Known gaps

tl;dv’s API has no team or user list, seats, roles, pending invites, last-active, SSO or 2FA, connected calendars or integrations, API-key list, webhook list or audit log. Webhooks can be set up (user, team or organization level) but cannot be listed through the API, so none of that is collected. duration is stored as tl;dv returns it; the docs do not state the unit.

What isn’t collected

  • Meeting titles, URLs and recording or download links
  • Transcripts, notes, highlights and AI summaries. Configview never calls those endpoints
  • Invitee names and email addresses. Only counts are kept
  • Template names and the free-form metadata field