LaunchDarkly REST API

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

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi CdapiKey105 Endpoints

Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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.

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 attributes

GET STARTED

Start building with LaunchDarkly REST API

Explore with Jentic

View OpenAPI Document

For Agents

Manage LaunchDarkly feature flags, environments, segments, and audit history through the REST API.

Use for: I need to turn on a feature flag in production, Create a new feature flag for the checkout-redesign rollout, Add a segment that targets users in beta-cohort, List the last 50 audit log entries for project p_abc

Not supported: Does not handle SDK flag evaluation traffic, log streaming, or product analytics - use for feature flag, audit, and admin control only.

Use Cases

Patterns agents use LaunchDarkly REST 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.

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 entries 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 for project p_abc in the last 30 days, filter for kind='flag', and write the results to the SIEM.

Streaming Evaluation Events to a Warehouse

An analytics team configures a Data Export destination so every flag evaluation streams into Kinesis or Pub/Sub for downstream analysis. The destinations endpoints register the target, enable it per environment, and return the configuration for management. Useful for joining flag exposure with product metrics in a warehouse.

Create a Data Export destination targeting Kinesis stream 'ld-evals' for project p_abc and environment production, then verify it is enabled.

AI Agent Release Manager

An AI agent operating as a release manager flips flags, queries audit history, and reports rollout status 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 access token handling. This lets an agent run progressive delivery and audit pulls with a single tool 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

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

METHOD

PATH

DESCRIPTION

GET

/auditlog

List audit log entries across the account.

GET

/auditlog/{resourceId}

Get audit history for a specific resource.

GET

/destinations

List Data Export destinations.

GET

/account/relay-auto-configs

List Relay Proxy auto-config entries.

POST

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

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

GET

/flag-status/{projectKey}/{featureFlagKey}

Get the rollout status of a specific feature flag.

GET

/auditlog

List audit log entries across the account.

GET

/auditlog/{resourceId}

Get audit history for a specific resource.

GET

/destinations

List Data Export destinations.

GET

/account/relay-auto-configs

List Relay Proxy auto-config entries.

POST

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

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

Why Jentic?

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

Credential isolation

Your LaunchDarkly access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check a flag status' or 'read the audit log', and Jentic returns the matching LaunchDarkly REST operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using LaunchDarkly REST 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 with Jentic One, the self-hosted execution layer.

What authentication does the LaunchDarkly REST API use?

The API uses an access token passed in the Authorization header. Through Jentic, the 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 accept JSON Patch operations to flip a flag on or off in a specific environment, change targeting rules, or adjust percentage rollouts - all without a redeploy.

What are the rate limits for the LaunchDarkly REST API?

LaunchDarkly applies per-account and per-endpoint rate limits returned in X-RateLimit-* response headers; the spec does not list exact thresholds. Read those headers and back off when limits are approached.

How do I query the audit log through Jentic?

Search Jentic for 'launchdarkly audit log', load the GET /auditlog operation, and filter by project, kind, and time range. The response paginates so the agent should follow nextPage links until empty.

Can I configure Data Export destinations with the LaunchDarkly REST API?

Yes. The /destinations endpoints register a destination such as Kinesis or Pub/Sub, scope it to a project and environment, and return the configuration for later updates.

Can I limit what my agent is allowed to do with the LaunchDarkly REST API?

Yes. Jentic One runs self-hosted, so your own rules decide which LaunchDarkly operations and which stored access token the agent may use. Because LaunchDarkly puts the project key in the URL path, such as /flag-status/{projectKey}/{featureFlagKey}, you can pin the agent to a single project and let it only read flag status and the audit log for that project. Higher-impact operations like resetting a Relay Proxy auto-config are called only if you explicitly add them to the allowed set.