Skip to main content
Telara

Integrations / LaunchDarkly

LaunchDarkly logo

LaunchDarkly

LaunchDarkly feature management for projects, environments, feature flags, segments, members, teams, and audit events.

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

A LaunchDarkly account you can administer.

Vendor setup

Get the credential

1
Prefer Connect
Settings → Integrations → LaunchDarkly. Approve access.
2
Token fallback
In LaunchDarkly, Account settings → Authorization. Create a personal or service token and paste it in Telara.

In Telara

Connect in Telara

OAuth 2.0

LaunchDarkly OAuth client credentials.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

API key

LaunchDarkly personal or service access token.

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

Fields Telara asks for
  • API token

Knowledge

What gets indexed

ResourceCoverage
ProjectsPartial — not every record the vendor holds is synced
Feature flagPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
ProjectsUp to 1 dayRemoved records disappear on the next full sync
Feature flagUp to 1 hourRemoved records disappear on the next full sync

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.

Excluded from semantic search: Projects, Feature flag.

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 client-side ID cannot call the admin APIs Telara uses.
Reader vs writer tokens change what Telara can list.