FAQ

What breaks if LD-API-Version stays 20220603 after 2026-12-31?

Official guidance states 20220603 reaches end of life on that day and you must upgrade to 20240415. Clients that keep the old version risk refused or undefined REST behavior. Treat Dec 31 as a hard inventory cut, then verify on the live migration guide rather than tribal memory.

Do I create a new token or only set the LD-API-Version header?

Either works. New tokens default to 20240415. Best practice is to set the header explicitly on every client so token defaults cannot silently drift. Many teams dual-run a new token then retire the old one after smoke tests.

Which list endpoints become paginated and what are default/max limits?

Access tokens, custom roles, feature flags, segments, and workflows move to paginated results in 20240415. Defaults are typically around 20–25; maxima differ (flags max 100, segments max 50, tokens max 1000, workflows max 200). Always page with limit and offset.

What replaces the removed Users and User settings APIs?

Use Contexts search and get APIs plus Context settings for flag overrides. Several User settings operations have no direct public equivalent—plan SDK evaluation details or Contexts list deletes instead of assuming a one-to-one REST swap.

Are LaunchDarkly SDKs also EOL as part of this change?

No. The migration guide states SDKs are not deprecated by this REST versioning work. Only REST API version 20220603 is ending. Do not schedule an unrelated SDK rewrite solely because of this EOL.

Does this tool call LaunchDarkly or rotate my tokens for me?

No. This is a local checklist and Markdown exporter. It does not create tokens, call LaunchDarkly, or scrape your projects.

Is this official LaunchDarkly documentation?

No. Unofficial local helper. Not affiliated with LaunchDarkly.

Do you store my answers or tokens?

No. Choices stay in the browser session; Copy Markdown uses the clipboard API only. We never ask for access tokens.