LaunchDarkly REST API

Name: LaunchDarkly REST API API
Brand: LaunchDarkly REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi CdapiKey355 EndpointsREST

For Agents

Manage LaunchDarkly feature flags, environments, experiments, contexts, and access controls programmatically through the v2 REST API.

Connect the LaunchDarkly REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LaunchDarkly REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with LaunchDarkly REST API API.

Create or update a feature flag and its variations across environments

Toggle a flag on or off in a specific environment without redeploying

Manage segments and rules that target users by context attributes

Submit, approve, or reject change approvals against a flag

GET STARTED

Start building with LaunchDarkly REST API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for LaunchDarkly REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for LaunchDarkly REST API, keeping it validated and agent-ready. The LaunchDarkly REST API (v2) covers feature flag and experimentation management — projects, environments, feature flags, segments, contexts, AI Configs, approvals, audit logs, code references, account members, custom roles, applications, and Data Export destinations. It is the platform-wide control plane for releasing software safely behind flags and running experiments. The spec covers 355 operations across the entire LaunchDarkly product surface.

Use Cases

Patterns agents use LaunchDarkly REST API API for, with concrete tasks.

★ Programmatic Flag Rollouts

A release tool flips a feature flag from 0 percent to 25 percent of traffic in production by calling the flag and environment endpoints, gradually expanding exposure based on health metrics. The API supports targeting rules, percentage rollouts, and per-environment overrides so a single flag can be progressed independently across staging and production. Teams use this to automate canaries without redeploying.

Update the 'checkout-redesign' flag in the production environment to a 25 percent rollout, then query the flag state to confirm the new rule is active.

Audit and Compliance Reporting

A compliance team pulls the LaunchDarkly audit log to produce evidence of who changed which flag, when, and why for SOC 2 and ISO 27001 audits. The audit log endpoints return changes filtered by project, environment, kind, and time window, which can be persisted into a SIEM. Useful for change-management evidence on regulated systems.

Pull every audit log entry from /api/v2 for project p_abc in the last 30 days, filter for kind='flag', and write the results to the SIEM.

Approval-Gated Production Changes

A team requires approvals on any production flag change. The Approvals endpoints submit a request, send it to designated reviewers, and apply the change only after sign-off. Combined with custom roles, this enforces separation of duties on high-risk flags.

Submit an approval request to change the 'billing-v2' flag in production, route it to the on-call lead, and apply the change once approval is granted.

AI Config Rollouts for LLM Apps

A team versioning prompts and models for an LLM-backed product manages them as AI Configs in LaunchDarkly, rolling out a new prompt to 10 percent of users via the same flag rules used for code. The AI Configs endpoints expose versions and targeting so prompt iteration ships safely. Useful when prompt changes need the same release governance as code.

Create a new AI Config version with the candidate prompt, target it to 10 percent of users in production, and monitor the audit log for any rule changes.

AI Agent Release Manager

An AI agent operating as a release manager flips flags, submits approvals, and reads the audit log via the LaunchDarkly REST API through Jentic. The agent searches Jentic for flag toggling, loads the operation schema, and executes the change without manually wiring LaunchDarkly's API key handling. This lets an agent run progressive delivery and audit pulls with the same call surface.

Use Jentic to call LaunchDarkly, advance the canary flag to the next rollout step in production, and post a summary of the change to the team channel.

Key Endpoints

355 endpoints — jentic publishes the only available openapi specification for launchdarkly rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v2/applications

List applications tracked in LaunchDarkly.

GET

/api/v2/approval-requests

List approval requests across the account.

POST

/api/v2/approval-requests/{id}

Apply or comment on an approval request.

GET

/api/v2/account/relay-auto-configs

List Relay Proxy auto-config entries.

POST

/api/v2/account/relay-auto-configs/{id}/reset

Reset the SDK key on a Relay Proxy auto-config.

GET

/api/v2/applications

List applications tracked in LaunchDarkly.

GET

/api/v2/approval-requests

List approval requests across the account.

POST

/api/v2/approval-requests/{id}

Apply or comment on an approval request.

GET

/api/v2/account/relay-auto-configs

List Relay Proxy auto-config entries.

POST

/api/v2/account/relay-auto-configs/{id}/reset

Reset the SDK key on a Relay Proxy auto-config.

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

LaunchDarkly access tokens are stored encrypted in the Jentic vault. Agents receive scoped tokens at execution time so the raw API key never enters the agent context.

Intent-based discovery

Agents search by intent (e.g., 'toggle a feature flag') and Jentic returns the matching LaunchDarkly REST operation with its input schema, so the agent can call the right endpoint without paging through 355 paths.

Time to first call

Direct LaunchDarkly integration: 1-2 days for token handling, JSON Patch payloads, and approval flow plumbing. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Split

Split offers feature flag and experimentation tooling with strong impact analysis.

Choose Split when the team prioritises built-in metric impact analysis on every flag rollout.

Alternative

ConfigCat

ConfigCat is a simpler, lower-cost feature flag service with a generous free tier.

Choose ConfigCat when LaunchDarkly's enterprise feature surface is more than the team needs.

Alternative

Statsig

Statsig combines feature flags with built-in product analytics and experimentation.

Choose Statsig when flagging and product analytics need to live in one tool with shared metrics.

Alternative

Optimizely

Optimizely focuses on experimentation and personalisation alongside feature flags.

Choose Optimizely when web personalisation and A/B testing matter more than flag-driven release governance.

FAQs

Specific to using LaunchDarkly REST API API through Jentic.

Why is there no official OpenAPI spec for LaunchDarkly REST API?

LaunchDarkly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LaunchDarkly REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the LaunchDarkly REST API use?

The API uses an API key passed in the Authorization header. Through Jentic, the LaunchDarkly access token lives in the encrypted vault and is injected at execution time so the raw token never appears in the agent context.

Can I toggle a feature flag with the LaunchDarkly REST API?

Yes. The flag endpoints under /api/v2 accept JSON Patch operations to flip a flag on or off in a specific environment, change targeting rules, or adjust percentage rollouts without a redeploy.

What are the rate limits for the LaunchDarkly REST API?

LaunchDarkly applies a global per-account rate limit and per-endpoint limits that are returned in X-RateLimit-* response headers; the spec does not enumerate exact numbers. Read those headers to back off when the limit is approached.

How do I submit a flag approval request through Jentic?

Search Jentic for 'submit a feature flag approval', load the operation under /api/v2/approval-requests, and POST the change with the target reviewers. Once approved, call the apply endpoint to commit the change.

Can I manage AI Configs with the LaunchDarkly REST API?

Yes. The AI Configs endpoints expose versions and targeting so a prompt or model can be rolled out to a percentage of users using the same governance as code flags.