How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Unleash Playground API

Evaluate an Unleash context against your feature flags.

Unleash Playground API is one of 36 APIs that Unleash publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Playground. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 3 paths, and defines 16 schemas. It is described by OpenAPI 3.0.3, at version 7.4.1.

Requests are made against a single base URL, https://app.unleash-instance.example.com.

3 operations 3 paths 16 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
7.4.1
Base URL
https://app.unleash-instance.example.com
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Unleash Playground API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (apiKey). It accepts HTTP bearer tokens (bearerToken). By default, every request must be authenticated.

  • apiKey — API key needed to access this API
  • bearerToken — API key needed to access this API, in Bearer token format

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Playground 3

Evaluate an Unleash context against your feature flags.

POST
/api/admin/playground/change-request/{id}
Evaluate an Unleash Context Against a Change Request Preview.
getChangeRequestPlayground 1 param body → 200400401404
POST
/api/admin/playground
Evaluate an Unleash Context Against a Set of Environments and Projects.
getPlayground body → 200400401
POST
/api/admin/playground/advanced
Batch Evaluate an Unleash Context Against a Set of Environments and Projects.
getAdvancedPlayground body → 200400401

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are advancedPlaygroundEnvironmentFeatureSchema (9 properties), playgroundStrategySchema (9 properties), playgroundFeatureSchema (8 properties), sdkContextSchema (7 properties). Each schema is shown below with its type and property counts.

advancedPlaygroundEnvironmentFeatureSchema
object
A simplified feature flag model intended for the Unleash playground.
9 properties 9 required
playgroundResponseSchema
object
The state of all features given the provided input.
2 properties 2 required
playgroundRequestSchema
object
Data for the playground API to evaluate feature flags
3 properties 2 required
overrideSchema
object
An override for deciding which variant should be assigned to a user based on the context name
2 properties 2 required
parametersSchema
object
A list of parameters for a strategy
changeRequestPlaygroundRequestSchema
object
Data for the playground API to evaluate flags with change request applied in preview mode
1 property 1 required
sdkContextSchema
object
The Unleash context as modeled in client SDKs
7 properties 1 required
sdkFlatContextSchema
object
The Unleash context with flattened properties
6 properties 1 required
playgroundFeatureSchema
object
A simplified feature flag model intended for the Unleash playground.
8 properties 7 required
advancedPlaygroundFeatureSchema
object
A simplified feature flag model intended for the Unleash playground.
3 properties 3 required
playgroundConstraintSchema
object
A strategy constraint. For more information, refer to [the strategy constraint reference documentation](https://docs.getunleash.io/concepts/activation-strategi…
7 properties 3 required
playgroundSegmentSchema
object
The evaluated result of a segment as used by the Playground.
4 properties 4 required
advancedPlaygroundResponseSchema
object
The state of all features given the provided input.
3 properties 2 required
playgroundStrategySchema
object
An evaluated feature flag strategy as used by the Playground
9 properties 8 required
advancedPlaygroundRequestSchema
object
Data for the playground API to evaluate toggles in advanced mode with environment and context multi selection
3 properties 2 required
variantSchema
object
A variant allows for further separation of users into segments. See [our excellent documentation](https://docs.getunleash.io/concepts/feature-flag-variantswhat…
6 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unleash-playground-api-openapi.yml Raw ↑

Other APIs Unleash publishes across the network.

Unleash Client API
Unleash Addons API
Unleash Admin UI API
Unleash API tokens API
Unleash Archive API
Unleash Auth API
Unleash Banners API
Unleash Change Requests API
Unleash Context API
Unleash Dependencies API
Unleash Environments API
Unleash Events API
Where this information came from

This is an independent, third-party profile of Unleash Playground API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.