---
title: "Get big segment membership for user"
method: GET
path: "/api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/users/{userKey}"
tags: ["Segments"]
---

# Get big segment membership for user

`GET /api/v2/segments/{projectKey}/{environmentKey}/{segmentKey}/users/{userKey}`

> ### 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.

## Path parameters

- `projectKey` string, string, required — The project key
- `environmentKey` string, string, required — The environment key
- `segmentKey` string, string, required — The segment key
- `userKey` string, string, required — The user key

## Response `200`

Segment membership for user response

- BigSegmentTarget
  - `userKey` string, required — The target key
  - `included` boolean, required — Indicates whether the target is included.<br />Included targets are always segment members, regardless of segment rules.
  - `excluded` boolean, required — Indicates whether the target is excluded.<br />Segment rules bypass excluded targets, so they will never be included based on rules. Excluded targets may still be included explicitly.

## Other responses

- `400` — Invalid request
- `401` — Invalid access token
- `404` — Invalid resource identifier
- `429` — Rate limited

---

[API](https://skmtc.dev/launchdarkly/apis/launchdarkly-rest-api.md) · [All operations](https://skmtc.dev/launchdarkly/apis/launchdarkly-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/launchdarkly/launchdarkly-rest-api/revisions/69c5c9aafe78/schema)