Skip to main content
Telara

Integrations / Langdock

Langdock logo

Langdock

Langdock usage export (POST /export/users). Enterprise AI workspace spend. Authority: apis.io langdock OpenAPI — Bearer only (no public OAuth).

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 Langdock workspace you can administer.
Admin who can issue API keys.

Vendor setup

Get the credential

1
Open API keys
Sign in to Langdock. Open Workspace settings → API Keys.
2
Create a key
Click Create API Key. Name it for Telara. Copy it immediately.
3
Paste in Telara
Settings → Integrations → Langdock. Paste the 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: Per user per day.

Attribution: Matched to people by email.

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

  • messages
    count
  • tokens
    tokens

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 builder key that cannot read workspace analytics produces empty spend.
This is Langdock’s admin API, not an OTLP exporter.