LaunchDarkly

Feature management platform for controlling feature rollouts with flags, targeting rules, and experimentation. Browse projects, environments, flags, metrics, and audit history.

Entity Hierarchy

Everything is scoped by project_key. Copy a working project_key from the project directory before querying project-level resources.

• Projects — top-level containers. Each has a unique key (URL-safe slug) and contains environments and flags. Enumerate projects first to discover available project_key values.
• Environments — deployment contexts within a project (e.g., production, staging, test). Each has its own SDK key and flag states. Requires project_key.
• Flags — feature toggles within a project. Each flag has a key, variations (boolean, string, number, or JSON), and per-environment targeting rules. Flag directory reads support filter (search by name/key), sort, and summary mode. Open one flag by key, optionally with env to include environment-specific state. Requires project_key.
• Metrics — experiment metrics and goals defined within a project. Used for measuring flag impact. Requires project_key.
• Members — account-level users with roles and permissions. Not project-scoped.
• Audit Log — chronological record of all configuration changes across the account. Filter by time range (after/before unix timestamps), resource spec, or keyword search q. Each entry shows who changed what, when, and the before/after state.

Workflows

• Flag inventory: Project listing → copy a project_key → flag directory (optionally summary mode + text filter) → single-flag read with environment overlay when you need per-env targeting.
• Environment comparison: Enumerate environments under one project to contrast dev/staging/prod wiring.
• Change audit: Audit log pulls with after/before windows plus resource spec filters to reconstruct flag edits.
• Experiment review: Metric directory for the project defines what success measures feed experiments.
• Team management: Member directory for roles and access posture.

Gotchas

• project_key is required for environments, flags, and metrics — always enumerate projects first.
• Flag keys are immutable: once created, a flag's key cannot be changed. It's the identifier used in SDKs.
• Pagination: Paged lists use offset + limit (default ~20); totalCount tells you if another page exists.
• Rate limits: About 10 reads/sec—pace automation accordingly.