For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
13.5kProductPricingSign inStart free trialBook a demo
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
    • API overview
  • Client API
  • Frontend API
  • Admin API
      • GETGets configured context fields
      • POSTCreate a context field
      • GETGets context field
      • PUTUpdate an existing context field
      • DELDelete an existing context field
      • POSTAdd or update legal value for the context field
      • DELDelete legal value for the context field
      • POSTValidate a context field
      • GET[BETA] Gets configured context fields
      • POST[BETA] Create a context field
      • GET[BETA] Gets context field
      • PUT[BETA] Update an existing context field
      • DEL[BETA] Delete an existing context field
      • POST[BETA] Add or update legal value for the context field
      • DEL[BETA] Delete legal value for the context field
      • POST[BETA] Validate a context field

Unleash reduces the risk of releasing new features, drives innovation by streamlining the software release process, and increases revenue by optimizing end-user experience. While we serve the needs of the world's largest, most security-conscious organizations, we are also rated the “Easiest Feature Management system to use” by G2.

GitHubGitHubLinkedInLinkedInX (Twitter)X (Twitter)SlackSlackStack OverflowStack OverflowYouTubeYouTube

Server SDKs

  • Node.js
  • Java
  • Go
  • Rust
  • Ruby
  • Python
  • .NET
  • PHP
  • All SDKs

Frontend SDKs

  • JavaScript
  • React
  • Next.js
  • Vue
  • iOS
  • Android
  • Flutter

Feature Flag use cases

  • Secure, scalable feature flags
  • Rollbacks
  • FedRAMP, SOC2, ISO2700 compliance
  • Progressive or gradual rollouts
  • Trunk-based development
  • Software kill switches
  • A/B testing
  • Feature management
  • Canary releases

Product

  • Quickstart
  • Unleash architecture
  • Pricing
  • Product vision
  • Open live demo
  • Open source
  • Enterprise feature management platform
  • Unleash vs LaunchDarkly

Support

  • Help center
  • Status
  • Changelog
Made in a cosy atmosphere in the Nordic countries.Copyright © 2026 Unleash
LogoLogo
13.5kProductPricingSign inStart free trialBook a demo
Admin APIContext

[BETA] Gets configured context fields

||View as Markdown|
GET
https://app.unleash-instance.example.com/api/admin/projects/:projectId/context
GET
/api/admin/projects/:projectId/context
$curl https://app.unleash-instance.example.com/api/admin/projects/projectId/context \
>     -H "Authorization: <apiKey>"
200Retrieved
1[
2  {
3    "name": "userId",
4    "description": "Used to uniquely identify users",
5    "stickiness": true,
6    "sortOrder": 900,
7    "createdAt": "2023-06-29T10:19:00.000Z",
8    "usedInFeatures": 3,
9    "usedInProjects": 2,
10    "legalValues": [
11      {
12        "value": "#c154c1",
13        "description": "Deep fuchsia"
14      }
15    ],
16    "project": "my-project"
17  }
18]
**[BETA]** This API is in beta state, which means it may change or be removed in the future. Returns all configured [Context fields](https://docs.getunleash.io/concepts/unleash-context) that have been created.
Was this page helpful?
Previous

[BETA] Create a context field

Next
Built with

[BETA] This API is in beta state, which means it may change or be removed in the future.

Returns all configured Context fields that have been created.

Authentication

Authorizationstring
API key needed to access this API
OR
AuthorizationBearer
API key needed to access this API, in Bearer token format

Path parameters

projectIdstringRequired

Query parameters

includestringOptional
Whether the response should include project-specific or root context fields in addition to the fields in the default response. When querying the root context API, `include=project` will yield a response that includes all project-specific context fields in addition to all root context fields. Conversely, when querying a project-specific context API, using `include=root` will yield a response that includes all root context fields in addition to the project-specific context fields. The other combinations have no effect, because the responses already include those fields. When including project-specific context fields via the root-level API, context fields in private projects the user does not have access to will be omitted.

Response

contextFieldsSchema
namestring
The name of the context field
descriptionstring or null
The description of the context field.
stickinessboolean

Does this context field support being used for stickiness calculations

sortOrderinteger
Used when sorting a list of context fields. Is also used as a tiebreaker if a list of context fields is sorted alphabetically.
createdAtstring or nullformat: "date-time"
When this context field was created
usedInFeaturesinteger or null>=0
Number of projects where this context field is used in
usedInProjectsinteger or null>=0
Number of projects where this context field is used in
legalValueslist of objects
Allowed values for this context field schema. Can be used to narrow down accepted input
projectstring

The project this context field belongs to (if it is project-specific)

Whether the response should include project-specific or root context fields in addition to the fields in the default response. When querying the root context API, include=project will yield a response that includes all project-specific context fields in addition to all root context fields. Conversely, when querying a project-specific context API, using include=root will yield a response that includes all root context fields in addition to the project-specific context fields. The other combinations have no effect, because the responses already include those fields. When including project-specific context fields via the root-level API, context fields in private projects the user does not have access to will be omitted.