Managing SDK keys is now more flexible. Each LaunchDarkly environment can support multiple SDK keys, giving you the tools to rotate keys without downtime, isolate access across services or teams, and set expiration dates to enforce key rotation policies.

Each key now has its own name, description, and optional expiration date. Fine-grained custom role support means you can control who can view or manage individual keys — down to the key level.

You can manage keys through the updated UI (Settings → Security → SDK Keys) or via API.

A note on backward compatibility: Each environment maintains a default non-expiring key to preserve existing behavior. Legacy reset endpoints and environment-level key fields will be deprecated in a future API version — if you rely on those workflows, now is a good time to plan your migration.

Docs