Contexts are now available
After you have upgraded your LaunchDarkly SDK to use contexts instead of users, you should use Update expiring targets for segment instead of this endpoint. To learn more, read Contexts.
Update expiring user targets for a segment. Updating a user target expiration uses the semantic patch format.
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.
If the request is well-formed but any of its instructions failed to process, this operation returns status code 200. In this case, the response errors array will be non-empty.
Semantic patch requests support the following kind instructions for updating expiring user targets.
Schedules a date and time when LaunchDarkly will remove a user from segment targeting.
targetType: A segment’s target type, must be either included or excluded.userKey: The user key.value: The date when the user should expire from the segment targeting, in Unix milliseconds.Updates the date and time when LaunchDarkly will remove a user from segment targeting.
targetType: A segment’s target type, must be either included or excluded.userKey: The user key.value: The new date when the user should expire from the segment targeting, in Unix milliseconds.version: The segment version.Removes the scheduled expiration for the user in the segment.
targetType: A segment’s target type, must be either included or excluded.userKey: The user key.The project key
The environment key
The segment key
Semantic patch instructions for the desired changes to the resource
Optional description of changes
Expiring user target response
An array of expiring user targets
The location and content type of related resources
The total count of instructions sent in the PATCH request
The total count of successful instructions sent in the PATCH request
The total count of the failed instructions sent in the PATCH request
An array of error messages for the failed instructions