Update flag settings for user

For the complete documentation index, see llms.txt. For the full documentation snapshot, see llms-full.txt.

Enable or disable a feature flag for a user based on their key.

Omitting the setting attribute from the request body, or including a setting of null, erases the current setting for a user.

If you previously patched the flag, and the patch included the user’s data, LaunchDarkly continues to use that data. If LaunchDarkly has never encountered the user’s key before, it calculates the flag values based on the user key alone.

PUT /api/v2/users/{projectKey}/{environmentKey}/{userKey}/flags/{featureFlagKey}

Update flag settings for user

cURL

curl --request PUT \
  --url https://app.launchdarkly.com/api/v2/users/{projectKey}/{environmentKey}/{userKey}/flags/{featureFlagKey} \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "setting": "existing_variation_value_to_use",
  "comment": "make sure this context experiences a specific variation"
}
'

400

{
  "code": "invalid_request",
  "message": "Invalid request body"
}

Authorizations

Authorization · string · header · required

Path Parameters

projectKey · string<string> · required

The project key

environmentKey · string<string> · required

The environment key

userKey · string<string> · required

The user key

featureFlagKey · string<string> · required

The feature flag key

Body

application/json

setting · any

The variation value to set for the context. Must match the flag's variation type.

Example:

"existing_variation_value_to_use"

comment · string

Optional comment describing the change

Example:

"make sure this context experiences a specific variation"

Response

204

Action succeeded