Get all features in a project
GET/api/admin/projects/:projectId/features
A list of all features for the specified project.
Request
Path Parameters
Responses
- 200
- 400
- 401
- 403
projectFeaturesSchema
- application/json
- Schema
- Example (from schema)
Schema
Array [
Array [
]
Array [
]
]
The version of the feature's schema
features
object[]
required
A list of features
Unique feature name
disable-comments
Type of the flag e.g. experiment, kill-switch, release, operational, permission
kill-switch
Detailed description of the feature
Controls disabling of the comments section in case of an incident
true
if the feature is stale based on the age and feature type, otherwise false
.
false
true
if the feature was favorited, otherwise false
.
true
true
if the impression data collection is enabled for the feature, otherwise false
.
false
The date the feature was created
2023-01-28T15:21:39.975Z
The date and time when metrics where last collected for this flag in any environment. This field was deprecated in v5. You should instead use the lastSeenAt
property on the individual environments listed under the environments
property.
2023-01-28T16:21:39.975Z
environments
object[]
required
The list of environments where the feature can be used
The name of the environment
my-dev-env
The type of the environment
development
true
if the feature is enabled for the environment, otherwise false
.
true
The sort order of the feature environment in the feature environments list
3
The number of defined variants
The date when metrics where last collected for the feature environment
2023-01-28T16:21:39.975Z
Whether the feature has any strategies defined.
Whether the feature has any enabled strategies defined.
tags
object[]
nullable
The list of feature tags
The value of the tag.
Possible values: >= 2 characters
and <= 50 characters
a-tag-value
The type of the tag
Possible values: >= 2 characters
and <= 50 characters
simple
{
"version": 0,
"features": [
{
"name": "disable-comments",
"type": "kill-switch",
"description": "Controls disabling of the comments section in case of an incident",
"stale": false,
"favorite": true,
"impressionData": false,
"createdAt": "2023-01-28T15:21:39.975Z",
"environments": [
{
"name": "my-dev-env",
"type": "development",
"enabled": true,
"sortOrder": 3,
"variantCount": 0,
"lastSeenAt": "2023-01-28T16:21:39.975Z",
"hasStrategies": true,
"hasEnabledStrategies": true
}
],
"tags": [
{
"value": "a-tag-value",
"type": "simple"
}
]
}
]
}
The request data does not match what we expect.
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008
The name of the error kind
ValidationError
A description of what went wrong.
The request payload you provided doesn't conform to the schema. The .parameters property should be object. You sent [].
{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "ValidationError",
"message": "The request payload you provided doesn't conform to the schema. The .parameters property should be object. You sent []."
}
Authorization information is missing or invalid. Provide a valid API token as the authorization
header, e.g. authorization:*.*.my-admin-token
.
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008
The name of the error kind
AuthenticationRequired
A description of what went wrong.
You must log in to use Unleash. Your request had no authorization header, so we could not authorize you. Try logging in at /auth/simple/login.
{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "AuthenticationRequired",
"message": "You must log in to use Unleash. Your request had no authorization header, so we could not authorize you. Try logging in at /auth/simple/login."
}
The provided user credentials are valid, but the user does not have the necessary permissions to perform this operation
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008
The name of the error kind
NoAccessError
A description of what went wrong.
You need the "UPDATE_ADDON" permission to perform this action in the "development" environment.
{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "NoAccessError",
"message": "You need the \"UPDATE_ADDON\" permission to perform this action in the \"development\" environment."
}