Perform a partial update to a feature flag. The request body must be a valid semantic patch, JSON patch, or JSON merge patch. To learn more the different formats, read Updates.
To make a semantic patch request, you must append domain-model=launchdarkly.semanticpatch
to your Content-Type
header. To learn more, read Updates using semantic patch.
The body of a semantic patch request for updating feature flags takes the following properties:
comment
(string): (Optional) A description of the update.environmentKey
(string): (Required for some instructions only) The key of the LaunchDarkly environment.instructions
(array): (Required) A list of actions the update should perform. Each action in the list must be an object with a kind
property that indicates the instruction. If the action requires parameters, you must include those parameters as additional fields in the object. The body of a single semantic patch can contain many different instructions.Semantic patch requests support the following kind
instructions for updating feature flags.
These instructions require the environmentKey
parameter.
Sets the flag’s targeting state to Off.
Here’s an example:
Sets the flag’s targeting state to On.
Here’s an example:
These instructions require the environmentKey
parameter.
Several of the instructions for working with targeting and variations require flag rule IDs, variation IDs, or clause IDs as parameters. Each of these are returned as part of the Get feature flag response. The flag rule ID is the _id
field of each element in the rules
array within each environment listed in the environments
object. The variation ID is the _id
field in each element of the variations
array. The clause ID is the _id
field of each element of the clauses
array within the rules
array within each environment listed in the environments
object.
Adds the given clauses to the rule indicated by ruleId
.
ruleId
: ID of a rule in the flag.clauses
: Array of clause objects, with contextKind
(string), attribute
(string), op
(string), negate
(boolean), and values
(array of strings, numbers, or dates) properties. The contextKind
, attribute
, and values
are case sensitive. The op
must be lower-case.Here’s an example:
Adds the flag indicated by key
with variation variationId
as a prerequisite to the flag in the path parameter.
key
: Flag key of the prerequisite flag.variationId
: ID of a variation of the prerequisite flag.Here’s an example:
Adds a new targeting rule to the flag. The rule may contain clauses
and serve the variation that variationId
indicates, or serve a percentage rollout that rolloutWeights
, rolloutBucketBy
, and rolloutContextKind
indicate.
If you set beforeRuleId
, this adds the new rule before the indicated rule. Otherwise, adds the new rule to the end of the list.
clauses
: Array of clause objects, with contextKind
(string), attribute
(string), op
(string), negate
(boolean), and values
(array of strings, numbers, or dates) properties. The contextKind
, attribute
, and values
are case sensitive. The op
must be lower-case.
beforeRuleId
: (Optional) ID of a flag rule.
Either
variationId
: ID of a variation of the flag.or
rolloutWeights
: (Optional) Map of variationId
to weight, in thousandths of a percent (0-100000).rolloutBucketBy
: (Optional) Context attribute available in the specified rolloutContextKind
.rolloutContextKind
: (Optional) Context kind, defaults to user
Here’s an example that uses a variationId
:
Here’s an example that uses a percentage rollout:
Adds context keys to the individual context targets for the context kind that contextKind
specifies and the variation that variationId
specifies. Returns an error if this causes the flag to target the same context key in multiple variations.
values
: List of context keys.contextKind
: (Optional) Context kind to target, defaults to user
variationId
: ID of a variation on the flag.Here’s an example:
Adds user keys to the individual user targets for the variation that variationId
specifies. Returns an error if this causes the flag to target the same user key in multiple variations. If you are working with contexts, use addTargets
instead of this instruction.
values
: List of user keys.variationId
: ID of a variation on the flag.Here’s an example:
Adds values
to the values of the clause that ruleId
and clauseId
indicate. Does not update the context kind, attribute, or operator.
ruleId
: ID of a rule in the flag.clauseId
: ID of a clause in that rule.values
: Array of strings, case sensitive.Here’s an example:
Adds a variation to the flag.
value
: The variation value.name
: (Optional) The variation name.description
: (Optional) A description for the variation.Here’s an example:
Removes all individual targets from the variation that variationId
specifies. This includes both user and non-user targets.
variationId
: ID of a variation on the flag.Here’s an example:
Removes all individual user targets from the variation that variationId
specifies. If you are working with contexts, use clearTargets
instead of this instruction.
variationId
: ID of a variation on the flag.Here’s an example:
Removes the clauses specified by clauseIds
from the rule indicated by ruleId
.
ruleId
: ID of a rule in the flag.clauseIds
: Array of IDs of clauses in the rule.Here’s an example:
Removes the prerequisite flag indicated by key
. Does nothing if this prerequisite does not exist.
key
: Flag key of an existing prerequisite flag.Here’s an example:
Removes the targeting rule specified by ruleId
. Does nothing if the rule does not exist.
ruleId
: ID of a rule in the flag.Here’s an example:
Removes context keys from the individual context targets for the context kind that contextKind
specifies and the variation that variationId
specifies. Does nothing if the flag does not target the context keys.
values
: List of context keys.contextKind
: (Optional) Context kind to target, defaults to user
variationId
: ID of a flag variation.Here’s an example:
Removes user keys from the individual user targets for the variation that variationId
specifies. Does nothing if the flag does not target the user keys. If you are working with contexts, use removeTargets
instead of this instruction.
values
: List of user keys.variationId
: ID of a flag variation.Here’s an example:
Removes values
from the values of the clause indicated by ruleId
and clauseId
. Does not update the context kind, attribute, or operator.
ruleId
: ID of a rule in the flag.clauseId
: ID of a clause in that rule.values
: Array of strings, case sensitive.Here’s an example:
Removes a variation from the flag.
variationId
: ID of a variation of the flag to remove.Here’s an example:
Rearranges the rules to match the order given in ruleIds
. Returns an error if ruleIds
does not match the current set of rules on the flag.
ruleIds
: Array of IDs of all rules in the flag.Here’s an example:
Removes all existing prerequisites and replaces them with the list you provide.
prerequisites
: A list of prerequisites. Each item in the list must include a flag key
and variationId
.Here’s an example:
Removes all targeting rules for the flag and replaces them with the list you provide.
rules
: A list of rules.Here’s an example:
Removes all existing targeting and replaces it with the list of targets you provide.
targets
: A list of context targeting. Each item in the list includes an optional contextKind
that defaults to user
, a required variationId
, and a required list of values
.Here’s an example:
Removes all existing user targeting and replaces it with the list of targets you provide. In the list of targets, you must include a target for each of the flag’s variations. If you are working with contexts, use replaceTargets
instead of this instruction.
targets
: A list of user targeting. Each item in the list must include a variationId
and a list of values
.Here’s an example:
Replaces the clause indicated by ruleId
and clauseId
with clause
.
ruleId
: ID of a rule in the flag.clauseId
: ID of a clause in that rule.clause
: New clause
object, with contextKind
(string), attribute
(string), op
(string), negate
(boolean), and values
(array of strings, numbers, or dates) properties. The contextKind
, attribute
, and values
are case sensitive. The op
must be lower-case.Here’s an example:
Updates the default on or off variation of the flag.
onVariationValue
: (Optional) The value of the variation of the new on variation.offVariationValue
: (Optional) The value of the variation of the new off variationHere’s an example:
Updates the default or “fallthrough” rule for the flag, which the flag serves when a context matches none of the targeting rules. The rule can serve either the variation that variationId
indicates, or a percentage rollout that rolloutWeights
and rolloutBucketBy
indicate.
variationId
: ID of a variation of the flag.or
rolloutWeights
: Map of variationId
to weight, in thousandths of a percent (0-100000).rolloutBucketBy
: (Optional) Context attribute available in the specified rolloutContextKind
.rolloutContextKind
: (Optional) Context kind, defaults to user
Here’s an example that uses a variationId
:
Here’s an example that uses a percentage rollout:
Updates the default off variation to variationId
. The flag serves the default off variation when the flag’s targeting is Off.
variationId
: ID of a variation of the flag.Here’s an example:
Changes the prerequisite flag that key
indicates to use the variation that variationId
indicates. Returns an error if this prerequisite does not exist.
key
: Flag key of an existing prerequisite flag.variationId
: ID of a variation of the prerequisite flag.Here’s an example:
Updates the description of the feature flag rule.
description
: The new human-readable description for this rule.ruleId
: The ID of the rule. You can retrieve this by making a GET request for the flag.Here’s an example:
Updates whether or not LaunchDarkly tracks events for the feature flag associated with this rule.
ruleId
: The ID of the rule. You can retrieve this by making a GET request for the flag.trackEvents
: Whether or not events are tracked.Here’s an example:
Updates what ruleId
serves when its clauses evaluate to true. The rule can serve either the variation that variationId
indicates, or a percent rollout that rolloutWeights
and rolloutBucketBy
indicate.
ruleId
: ID of a rule in the flag.
variationId
: ID of a variation of the flag.
or
rolloutWeights
: Map of variationId
to weight, in thousandths of a percent (0-100000).
rolloutBucketBy
: (Optional) Context attribute available in the specified rolloutContextKind
.
rolloutContextKind
: (Optional) Context kind, defaults to user
Here’s an example:
Updates whether or not LaunchDarkly tracks events for the feature flag, for all rules.
trackEvents
: Whether or not events are tracked.Here’s an example:
Updates whether or not LaunchDarkly tracks events for the feature flag, for the default rule.
trackEvents
: Whether or not events are tracked.Here’s an example:
Updates a variation of the flag.
variationId
: The ID of the variation to update.name
: (Optional) The updated variation name.value
: (Optional) The updated variation value.description
: (Optional) The updated variation description.Here’s an example:
These instructions do not require the environmentKey
parameter. They make changes that apply to the flag across all environments.
Adds a new custom property to the feature flag. Custom properties are used to associate feature flags with LaunchDarkly integrations. For example, if you create an integration with an issue tracking service, you may want to associate a flag with a list of issues related to a feature’s development.
key
: The custom property key.name
: The custom property name.values
: A list of the associated values for the custom property.Here’s an example:
Adds tags to the feature flag.
values
: A list of tags to add.Here’s an example:
Marks the feature flag as permanent. LaunchDarkly does not prompt you to remove permanent flags, even if one variation is rolled out to all your customers.
Here’s an example:
Marks the feature flag as temporary.
Here’s an example:
Removes the associated values from a custom property. If all the associated values are removed, this instruction also removes the custom property.
key
: The custom property key.values
: A list of the associated values to remove from the custom property.Removes the flag’s maintainer. To set a new maintainer, use the updateMaintainerMember
or updateMaintainerTeam
instructions.
Here’s an example:
Removes tags from the feature flag.
values
: A list of tags to remove.Here’s an example:
Replaces the existing associated values for a custom property with the new values.
key
: The custom property key.name
: The custom property name.values
: A list of the new associated values for the custom property.Here’s an example:
Turns off client-side SDK availability for the flag. This is equivalent to unchecking the SDKs using Mobile key and/or SDKs using Client-side ID boxes for the flag. If you’re using a client-side or mobile SDK, you must expose your feature flags in order for the client-side or mobile SDKs to evaluate them.
value
: Use “usingMobileKey” to turn off availability for mobile SDKs. Use “usingEnvironmentId” to turn on availability for client-side SDKs.Here’s an example:
Turns on client-side SDK availability for the flag. This is equivalent to checking the SDKs using Mobile key and/or SDKs using Client-side ID boxes for the flag. If you’re using a client-side or mobile SDK, you must expose your feature flags in order for the client-side or mobile SDKs to evaluate them.
value
: Use “usingMobileKey” to turn on availability for mobile SDKs. Use “usingEnvironmentId” to turn on availability for client-side SDKs.Here’s an example:
Updates the feature flag description.
value
: The new description.Here’s an example:
Updates the maintainer of the flag to an existing member and removes the existing maintainer.
value
: The ID of the member.Here’s an example:
Updates the maintainer of the flag to an existing team and removes the existing maintainer.
value
: The key of the team.Here’s an example:
Updates the feature flag name.
value
: The new name.Here’s an example:
These instructions do not require the environmentKey
parameter. They make changes that apply to the flag across all environments.
Archives the feature flag. This retires it from LaunchDarkly without deleting it. You cannot archive a flag that is a prerequisite of other flags.
Deletes the feature flag and its rules. You cannot restore a deleted flag. If this flag is requested again, the flag value defined in code will be returned for all contexts.
Here’s an example:
Deprecates the feature flag. This hides it from the live flags list without archiving or deleting it.
Here’s an example:
Restores the feature flag if it was previously deprecated.
Here’s an example:
Restores the feature flag if it was previously archived.
Here’s an example:
If you do not include the semantic patch header described above, you can use a JSON patch or JSON merge patch representation of the desired changes.
In the JSON patch representation, use a JSON pointer in the path
element to describe what field to change. Use the Get feature flag endpoint to find the field you want to update.
There are a few special cases to keep in mind when determining the value of the path
element:
If a request attempts to alter a flag configuration in an environment where approvals are required for the flag, the request will fail with a 405. Changes to the flag configuration in that environment will require creating an approval request or a workflow.
If a flag configuration change made through this endpoint would cause a pending scheduled change or approval request to fail, this endpoint will return a 400. You can ignore this check by adding an ignoreConflicts
query parameter set to true
.
For migration flags, the cohort information is included in the rules
property of a flag’s response. You can update cohorts by updating rules
. Default cohort information is included in the fallthrough
property of a flag’s response. You can update the default cohort by updating fallthrough
.
When you update the rollout for a cohort or the default cohort through the API, provide a rollout instead of a single variationId
.
To learn more, read Migration flags.
The project key
The feature flag key. The key identifies the flag in your code.
If true, the patch will be applied even if it causes a pending scheduled change or approval request to fail.
A JSON patch representation of the change to make
Optional comment
Global flag response
A human-friendly name for the feature flag
Kind of feature flag
A unique key used to reference the flag in your code
Version of the feature flag
Timestamp of flag creation date
An array of possible variations for the flag
Whether the flag is a temporary flag
The location and content type of related resources
Experimentation data for the feature flag
Metadata attached to the feature flag, in the form of the property key associated with a name and array of values for the metadata to associate with this flag. Typically used to store data related to an integration.
Boolean indicating if the feature flag is archived
Details on the environments for this flag. Only returned if the request is filtered by environment, using the filterEnv
query parameter.
Description of the feature flag
Which type of client-side SDKs the feature flag is available to
Associated maintainerId for the feature flag
Associated maintainer member info for the feature flag
The key of the associated team that maintains this feature flag
Associated maintainer team info for the feature flag
If archived is true, date of archive
Boolean indicating if the feature flag is deprecated
If deprecated is true, date of deprecation
The indices, from the array of variations, for the variations to serve by default when targeting is on and when targeting is off. These variations will be used for this flag in new environments. If omitted, the first and last variation will be used.
Migration-related settings for the flag
Deprecated, use clientSideAvailability
. Whether this flag should be made available to the client-side JavaScript SDK
Deprecated, use experiments
instead