Contexts are now available
After you have upgraded your LaunchDarkly SDK to use contexts instead of users, you should use Contexts instead of these endpoints. To learn more, read Contexts.
This feature is in beta
To use this feature, pass in a header including the
LD-API-Version
key with value set tobeta
. Use this header with each call. To learn more, read Beta resources.Resources that are in beta are still undergoing testing and development. They may change without notice, including becoming backwards incompatible.
LaunchDarkly creates a record for each user passed in to variation
calls. This record powers the autocomplete functionality on the feature flag dashboard, as well as the Users page. To learn more, read Contexts
LaunchDarkly also offers an API that lets you access this data. You can use the users API to see what user data is available to LaunchDarkly, as well as determine which flag values a user will receive. You can also explicitly set which flag value a user will receive with this API.
Users are always scoped within both a project and an environment. Each environment has its own set of user records.
Use contexts instead
After you have upgraded your LaunchDarkly SDK to use contexts instead of users, you should use Get context attribute names instead of this endpoint.
Get all in-use user attributes in the specified environment. The set of in-use attributes typically consists of all attributes seen within the past 30 days.
User attribute names response
Invalid request
Invalid access token
Forbidden
Invalid resource identifier
{- "private": [
- "SSN",
- "credit_card_number"
], - "custom": [
- "Age",
- "FavoriteFood",
- "FavoriteColor"
], - "standard": [
- "key",
- "ip",
- "firstName",
- "lastName",
- "country",
- "anonymous"
]
}