How to run the LaunchDarkly REST 20220603 EOL checklist

Use this when you must move LaunchDarkly REST clients off API version 20220603 before 2026-12-31 onto 20240415, add pagination where lists became paginated, and retire Users APIs. The home tool stays in your browser and never calls LaunchDarkly. Always re-check the official migration guide before you treat a ticket as done.

1. Step 1. Confirm EOL and target version on the official guide. Note December 31, 2026 for 20220603 and the requirement to use 20240415. Do not rely only on this static site.
2. Step 2. Inventory every client that sets LD-API-Version or relies on access-token defaults. Search repos, gateways, and shared tokens for 20220603. Record owner and last deploy for each hit.
3. Step 3. Open the home checklist and answer axis A (version). Pick still on 20220603, already 20240415, or unknown. Wrong answers produce the wrong pack.
4. Step 4. Answer axis B (pagination). Mark whether list flags, segments, tokens, custom roles, or workflows still assume unpaginated full arrays.
5. Step 5. Answer axis C (Users API). Mark leftover Users / User settings calls versus Contexts migration or N/A.
6. Step 6. Build the action pack and copy Markdown into your migration ticket. Prefer setting LD-API-Version: 20240415 on every request, or create a new token pinned to 20240415.
7. Step 7. Implement pagination loops: increase offset by limit until items are empty or offset exceeds totalCount. Respect per-endpoint maxima (for example flags 100, segments 50).
8. Step 8. Replace Users APIs with Contexts equivalents, remove deleted flag filters, upgrade generated clients to ≥21.x when applicable, smoke-test, and attach official URLs beside the export.

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates.