▣ LD REST 20220603 EOL

Triple-axis REST version board · local · not a LaunchDarkly console

Check LD-API-Version:20220603, pagination, and Users API before EOL

A · Version header (EOL Dec 31, 2026)

B · Pagination on list endpoints

C · Users API usage

How it works

  1. Answer version-header, pagination, and Users-API status for your stack.
  2. Get a Dec 31 action checklist ranked for 20240415, limit/offset loops, and Contexts migration.
  3. Copy Markdown into your migration ticket — we never call LaunchDarkly APIs or rotate tokens.

Axis A tracks LD-API-Version: 20220603 end of life on 2026-12-31. Axis B tracks paginated list endpoints (flags, segments, tokens, custom roles, workflows). Axis C tracks removed Users / User settings APIs versus Contexts. Use all three so header migration does not hide truncated lists or dead Users calls.

vs LinkedIn dual-deadline / OpenAI Nov30 matrix: this is feature-flag REST versioning × pagination × Users→Contexts — not an ads YYYYMM×surface matrix and not an LLM platform shutdown grid.

Next: read the how-to, skim domain FAQ, or match a use case. Verify every date on the official LaunchDarkly REST migration guide before you close the ticket.