LaunchDarkly · Rate Limits

Launchdarkly Rate Limits

LaunchDarkly runs three concurrent rate-limit families on the REST API plus IP-based limiting, and DELIBERATELY does not publish the numbers. The published contract is the HEADERS, not the limits.

Launchdarkly Rate Limits is the machine-readable rate-limit profile for LaunchDarkly on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions.

Limit state is signalled in the limit, remaining, reset, and globalLimit response headers, and an exhausted limit returns HTTP 429.

The profile also includes response codes documented for throttled.

Tagged areas include Feature Flags, Feature Management, Experimentation, Observability, and Continuous Delivery.

4 Limits Exhausted: HTTP 429 limitremainingresetglobalLimit
Transcribed from the provider's documentation on 2026-08-27 — The "Rate limiting" section the provider maintains inside....
View Source
Feature FlagsFeature ManagementExperimentationObservabilityContinuous DeliveryDevOpsAI AgentsRelease ManagementDeveloper ToolsT1

Limits

Global account
· per 10 seconds
undisclosed/10 seconds
Account-wide. Exceeding it with one token degrades every other token on the account — which makes an unsupervised agent a shared-fate risk for the whole org.
Route-level route (URL pattern + verb)
· per 10 seconds
undisclosed (varies by route)/10 seconds
A route is one URL pattern and verb. DELETE /environments/{key} is one route; each call counts against that route's bucket regardless of which environment.
Access token token
· per 10 seconds
undisclosed/10 seconds
The only family that reports its own reset time in a dedicated header rather than the shared X-Ratelimit-Reset. Also the only family whose exhaustion does not affect other tokens — which is the argument for giving an agent its own service token rather than sharing one.
IP-based source IP
· per undisclosed
undisclosed/undisclosed
Applies to "some API routes". Returns Retry-After in seconds instead of the X-Ratelimit-* family. The provider explicitly instructs clients to wait at least Retry-After seconds and to apply jitter and backoff.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/launchdarkly-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.