Get big segment membership for user | LaunchDarkly

> ### Contexts are now available > > After you have upgraded your LaunchDarkly SDK to use contexts instead of users, you should use [Get expiring targets for segment](https://launchdarkly.com/docs/api/segments/get-expiring-targets-for-segment) instead of this endpoint. To learn more, read [Contexts](https://launchdarkly.com/docs/home/observability/contexts). Get the membership status (included/excluded) for a given user in this big segment. This operation does not support standard segments.

Contexts are now available

After you have upgraded your LaunchDarkly SDK to use contexts instead of users, you should use Get expiring targets for segment instead of this endpoint. To learn more, read Contexts.

Get the membership status (included/excluded) for a given user in this big segment. This operation does not support standard segments.

Authentication

Authorizationstring

API Key authentication via header

Path parameters

projectKeystringRequiredformat: "string"

The project key

environmentKeystringRequiredformat: "string"

The environment key

segmentKeystringRequiredformat: "string"

The segment key

userKeystringRequiredformat: "string"

The user key

Response

Segment membership for user response

userKeystring

The target key

includedboolean

Indicates whether the target is included.
Included targets are always segment members, regardless of segment rules.

excludedboolean

Indicates whether the target is excluded.
Segment rules bypass excluded targets, so they will never be included based on rules. Excluded targets may still be included explicitly.

Errors

400

Bad Request Error

401

Unauthorized Error

404

Not Found Error

429

Too Many Requests Error

Contexts are now available

After you have upgraded your LaunchDarkly SDK to use contexts instead of users, you should use Get expiring targets for segment instead of this endpoint. To learn more, read Contexts.

Get the membership status (included/excluded) for a given user in this big segment. This operation does not support standard segments.

API Key authentication via header

Segment membership for user response

Indicates whether the target is included.
Included targets are always segment members, regardless of segment rules.

Indicates whether the target is excluded.
Segment rules bypass excluded targets, so they will never be included based on rules. Excluded targets may still be included explicitly.

$	curl https://app.launchdarkly.com/api/v2/segments/projectKey/environmentKey/segmentKey/users/userKey \
>	-H "Authorization: <apiKey>"

1	{
2	"userKey": "string",
3	"included": true,
4	"excluded": true
5	}