LdApiEOL · Waitlist
Answer 5 quick questions — is LD-API-Version set, how old are your access tokens, which list endpoints you call, whether you still use the Users / User settings APIs, raw HTTP or generated client. Get a must-change list, pagination templates, a Users-to-Contexts mapping, and a regression checklist for 20240415. Not a LaunchDarkly connector — never paste tokens, SDK keys, or code.
Per LaunchDarkly's migration guide: API version 20220603 reaches end of life on December 31, 2026. All customers must use 20240415 from January 1, 2027.
Market-validation page · Free waitlist · No fake user counts · Not affiliated with LaunchDarkly · Never paste tokens, SDK keys, or code
Problem
Per LaunchDarkly's REST API migration guide, the 20220603 REST API version reaches its end of life on December 31, 2026 and can no longer be accessed after that; all customers will be required to use version 20240415 as of January 1, 2027. 20240415 is a breaking version: several list endpoints become paginated (read only the first page and you silently get fewer items), List feature flags loses filters and the compare parameter, and the Users, Users (beta), and User settings APIs are removed entirely. Your version comes from the LD-API-Version header on each request — or, if you never set it, from the version set on the access token when it was created.
| Endpoint | What changes | Default page size | limit cap |
|---|---|---|---|
List access tokens | Newly paginated Page with limit / offset until items is empty or offset is greater than totalCount. | 25 | 1000 |
List custom roles | Newly paginated Page with limit / offset until items is empty or offset is greater than totalCount. | 20 | 1000 |
List feature flags | Newly paginated Page with limit / offset. 10 filters and the compare parameter are removed; the environments field is only returned when you filter by environment. | 20 | 100 |
List segments | Newly paginated Page with limit / offset until items is empty or offset is greater than totalCount. | 20 | 50 |
Get workflows | Newly paginated Page with limit / offset. The response no longer includes the _conflicts field. | 20 | 200 |
List account members | Not newly paginated No longer supports the accessCheck filter; limit is capped at 1000. | — | 1000 |
List teams | Not newly paginated expand no longer supports projects or roles; limit is capped at 100. | — | 100 |
Removed from List feature flags in 20240415 (per the migration guide):
codeReferencescontextKindTargetedcontextKindsEvaluatedfollowerIdhasDataExporthasExperimentsegmentTargetedstatustargetingtargetingModifiedDatecompare
Source: LaunchDarkly REST API migration guide: 20220603 to 20240415 (checked 2026-09-27). Generated client library users must upgrade to 21.x or later. Always confirm on the official pages.
Solution
A 20220603 → 20240415 readiness decision layer for LaunchDarkly REST API users still on 20220603 (or sending no header): your version setup × the endpoints you call → must-change list + templates + Users→Contexts mapping + regression checklist. Not a replacement for the official docs, not a LaunchDarkly connector, and not affiliated with LaunchDarkly.
Platform engineering, DevOps, and internal-tools owners whose teams already pay for LaunchDarkly and manage flags, segments, members, custom roles, or access tokens through the REST API (scripts, CI, admin back-office, generated client) — still pinned to LD-API-Version: 20220603, or sending no header and relying on an old access token's default version.
20220603 reaches end of life on December 31, 2026; all customers must use 20240415 from January 1, 2027. 20240415 paginates List access tokens, List custom roles, List feature flags, List segments, and Get workflows; removes 10 List feature flags filters and compare; drops accessCheck from List account members; and removes the Users, Users (beta), and User settings APIs. The official docs are complete but long — there is no one-page "my version × my endpoints → what to fix tonight → how to test" tool.
Tick 5 questions → a personalized must-change list, limit/offset curl and pseudocode templates, the official Users→Contexts mapping, and a regression checklist, plus a waitlist. Never asks for LaunchDarkly access tokens, SDK keys, or source code; not a LaunchDarkly connector.
Before 2026-12-31, every script, CI job, and back-office tool is on 20240415: you know which calls break, how to add the pagination loop, which Contexts endpoint replaces each Users call, and what to test before release — instead of firefighting on 2027-01-01 when release gates, sync jobs, and audit reports fail together.
| Removed Users / User settings endpoint | Replacement (per the migration guide) |
|---|---|
getSearchUsers | searchContextInstances |
getUsers | searchContexts |
getUser | getContextInstances |
deleteUser | deleteContextInstances |
getUserAttributeNames | getContextAttributeNames |
putFlagSetting | putContextFlagSetting |
patchExpiringFlagsForUser | patchExpiringTargets (semantic patch addExpiringTarget) |
getUserFlagSettings | No direct equivalent evaluateContextInstance may be equivalent in some situations. |
getUserFlagSetting | No direct equivalent Consider the SDK's flag variation evaluation details. |
getExpiringFlagsForUser | No direct equivalent |
The Users, Users (beta), and User settings APIs (deprecated May 2023) are removed in 20240415. getUserFlagSettings, getUserFlagSetting, and getExpiringFlagsForUser have no direct equivalent.
Features
Marketing points from the product hypothesis — for demand validation, not a formal spec promise.
Are you really on 20220603? Header vs token default, plus the two official fixes and the 21.x+ client note.
Paginated endpoints, removed List feature flags filters and compare, members accessCheck, teams expand limits.
limit/offset loops with the right cap per endpoint; token shown only as $LD_API_TOKEN placeholder.
Official one-to-one replacements, with "no direct equivalent" warnings.
Staging-first cutover steps and days left until Dec 31, 2026.
How it works
A three-step loop matching the waitlist-stage product hypothesis.
LD-API-Version set or not · token age / default version · list endpoints you call · Users / User settings API · raw HTTP or generated client.
Newly paginated endpoints (with default page size and limit caps), removed filters, and the official Users-to-Contexts mapping — including endpoints with no direct replacement. Every item links to the official docs.
limit/offset curl and pseudocode, the LD-API-Version: 20240415 fix, and a staging-to-prod checklist — never paste tokens, SDK keys, or code.
Use cases
If these situations sound familiar, join the waitlist to help us validate.
GET /api/v2/flags/{projectKey} with no pagination and more than 20 flags → after the upgrade you only see the first page. Needs a pagination loop template (limit cap 100) and a count-comparison test.
These filters are removed in 20240415. Needs a must-change list and a regression item for "filter on the client side instead".
Lists members, custom roles, and access tokens: members no longer support accessCheck; custom roles and access tokens become paginated. Needs a per-endpoint list.
Needs the Users→Contexts mapping, and to know up front which 3 endpoints have no direct equivalent.
Needs to work out the real version and decide: add the header everywhere, or switch to a new token.
Need to confirm the upgrade to 21.x+ and regression-test types and pagination behavior.
Public signals
Public LaunchDarkly documentation only — no customer quotes, endorsements, or invented metrics.
FAQ
No. LdApiEOL is independent and not affiliated with or endorsed by LaunchDarkly. Everything cites LaunchDarkly's public docs with links.
The guide lists every change. We filter to the version setup and endpoints you tick, and output a must-change list, templates, and a regression checklist.
Support answers individual cases; consultants run full projects. We are a lightweight self-serve static tool; the validation waitlist is free.
Then the version comes from the version set on your access token when it was created. If that is 20220603 or older, you may be affected. LaunchDarkly recommends setting the header explicitly on every request.
Switching the header (or creating a new 20240415 token) only changes the version. Pagination, removed filters, and the removed Users APIs still need code changes and retesting.
Per LaunchDarkly's guide, no SDKs are being deprecated as part of this change; it applies only to the REST API.
No. Never asked, never held, never stored. We don't connect to your LaunchDarkly account.
No. The MVP is a static questionnaire + must-change list + templates + checklist + waitlist.
Waitlist invites go out in batches by email. No fake launch date.
Assumed small readiness audit or team seat later; formal pricing comes with the launch email. The waitlist is free.
Waitlist
Leave your work email for LdApiEOL early access and launch notes. Checkboxes and selects only — never paste LaunchDarkly access tokens, SDK keys, mobile keys, or code in any field.
We'll email early-access invites and launch updates in batches (no promised launch date). Check your inbox for a confirmation email if enabled. Unsubscribe anytime.