Overview
Published on May 25th, 2026Introduction
The Context Store has several Launch Darkly templated Data Sources to allow users to quickly pull relevant data into their Data Store. These templates are a starting point and often you'll want to apply filters or chained Data Sources to modify these templates to suit your needs.
Authentication
The built-in launchdarkly integration uses token/header auth.
For broad compatibility with all LaunchDarkly seeds:
- Use a LaunchDarkly API token with read access to:
- projects, flags, environments, metrics
- members and teams
- audit log
- Scope project-level access to only the projects you need if applying least-privilege controls.
- If using custom roles/policies, validate each endpoint above with a quick manual request before enabling scheduled syncs.
LaunchDarkly access tokens are usually constrained by token role/policy and resource scope (account, projects, environments).
Pre-built Data Sources
This table lists the LaunchDarkly API permissions needed for the LaunchDarkly data source seeds currently defined in this repo.
| Data source seed | LaunchDarkly endpoint(s) used | Required token permission(s) |
|---|---|---|
LaunchDarkly projects | GET /api/v2/projects | Read access to projects |
LaunchDarkly feature flags | GET /api/v2/projects then GET /api/v2/flags/{projectKey} | Read access to projects and feature flags |
LaunchDarkly environments | GET /api/v2/projects then GET /api/v2/projects/{projectKey}/environments | Read access to projects and environments |
LaunchDarkly members | GET /api/v2/members | Read access to members |
LaunchDarkly teams | GET /api/v2/teams | Read access to teams |
LaunchDarkly audit log | GET /api/v2/auditlog | Read access to audit log |
LaunchDarkly metrics | GET /api/v2/projects then GET /api/v2/metrics/{projectKey} | Read access to projects and metrics |
