/api/admin/features
Most of this API was removed in Unleash v5 (after being deprecated since Unleash v4.3). You should use the project-based API (/api/admin/projects/:projectId) instead.
In order to access the admin API endpoints you need to identify yourself. Unless you're using the none authentication method, you'll need to create an admin token and add an Authorization header using the token.
Fetching Feature Toggles
This endpoint was removed in Unleash v5. Please use the project-based endpoint to fetch all toggles instead.
GET: http://unleash.host.com/api/admin/features
This endpoint is the one all admin ui should use to fetch all available feature toggles from the unleash-server. The response returns all active feature toggles and their current strategy configuration. A feature toggle will have at least one configured strategy. A strategy will have a name and parameters map.
Example response:
{
"version": 2,
"features": [
{
"name": "Feature.A",
"description": "lorem ipsum",
"type": "release",
"enabled": false,
"stale": false,
"strategies": [
{
"name": "default",
"parameters": {}
}
],
"variants": [
{
"name": "variant1",
"weight": 50
},
{
"name": "variant2",
"weight": 50
}
],
"tags": [
{
"id": 1,
"type": "simple",
"value": "TeamRed"
}
]
},
{
"name": "Feature.B",
"description": "lorem ipsum",
"enabled": true,
"stale": false,
"strategies": [
{
"name": "ActiveForUserWithId",
"parameters": {
"userIdList": "123,221,998"
}
},
{
"name": "GradualRolloutRandom",
"parameters": {
"percentage": "10"
}
}
],
"variants": [],
"tags": []
}
]
}
Filter feature toggles
Supports three params for now
tag- filters for features tagged with tagproject- filters for features belonging to projectnamePrefix- filters for features beginning with prefix
For tag and project performs OR filtering if multiple arguments
To filter for any feature tagged with a simple tag with value taga or a simple tag with value tagb use
GET https://unleash.host.com/api/admin/features?tag[]=simple:taga&tag[]simple:tagb
To filter for any feature belonging to project myproject use
GET https://unleash.host.com/api/admin/features?project=myproject
Response format is the same as api/admin/features
Fetch specific feature toggle
This endpoint was removed in Unleash v5 (deprecated since v4). Please use the project-based endpoint to fetch specific toggles instead.
GET: http://unleash.host.com/api/admin/features/:featureName
Used to fetch details about a specific featureToggle. This is mostly provded to make it easy to debug the API and should not be used by the client implementations.
{
"name": "Feature.A",
"description": "lorem ipsum..",
"type": "release",
"enabled": false,
"stale": false,
"strategies": [
{
"name": "default",
"parameters": {}
}
],
"variants": [],
"tags": []
}
Create a new Feature Toggle
This endpoint was removed in Unleash v5 (deprecated since v4). Please use the project-based endpoint to create feature toggles instead.
POST: http://unleash.host.com/api/admin/features/
Body:
{
"name": "Feature.A",
"description": "lorem ipsum..",
"type": "release",
"enabled": false,
"stale": false,
"strategies": [
{
"name": "default",
"parameters": {}
}
]
}
Used by the admin-dashboard to create a new feature toggles.
Notes:
- name must be globally unique, otherwise you will get a 403-response.
- type is optional. If not defined it defaults to
release
Returns 200-response if the feature toggle was created successfully.
Update a Feature Toggle
This endpoint was removed in Unleash v5. Please use the project-based endpoint to update a feature toggle instead.
PUT: http://unleash.host.com/api/admin/features/:toggleName
Body:
{
"name": "Feature.A",
"description": "lorem ipsum..",
"type": "release",
"enabled": false,
"stale": false,
"strategies": [
{
"name": "default",
"parameters": {}
}
],
"variants": []
}
Used by the admin dashboard to update a feature toggles. The name has to match an existing features toggle.
Returns 200-response if the feature toggle was updated successfully.
Tag a Feature Toggle
POST https://unleash.host.com/api/admin/features/:featureName/tags
Used to tag a feature
If the tuple (type, value) does not already exist, it will be added to the list of tags. Then Unleash will add a relation between the feature name and the tag.
Body:
{
"type": "simple",
"value": "Team-Green"
}
Success
- Returns _201-CREATED_ if the feature was tagged successfully
- Creates the tag if needed, then connects the tag to the existing feature
Failures
- Returns _404-NOT-FOUND_ if the `type` was not found
Remove a tag from a Feature Toggle
DELETE https://unleash.host.com/api/admin/features/:featureName/tags/:type/:value
Removes the specified tag from the (type, value) tuple from the Feature Toggle's list of tags.
Success
- Returns _200-OK_
Failures
- Returns 404 if the tag does not exist
- Returns 500 if the database could not be reached
Archive a Feature Toggle
This endpoint was removed in v5. Please use the project-based endpoint to archive toggles instead.
DELETE: http://unleash.host.com/api/admin/features/:toggleName
Used to archive a feature toggle. A feature toggle can never be totally be deleted, but can be archived. This is a design decision to make sure that a old feature toggle does not suddenly reappear because someone else is re-using the same name.
Enable a Feature Toggle
This endpoint was removed in v5. Please use the project-based endpoint to enable feature toggles instead.
POST: http://unleash.host.com/api/admin/features/:featureName/toggle/on
Used to enable a feature toggle. The :featureName must match an existing Feature Toggle. Returns 200-response if the feature toggle was enabled successfully.
Body
None
Example response:
{
"name": "Feature.A",
"description": "lorem ipsum..",
"type": "release",
"enabled": true,
"strategies": [
{
"name": "default",
"parameters": {}
}
],
"variants": [],
"tags": []
}
Disable a Feature Toggle
This endpoint was removed in v5. Please use the project-based endpoint to disable feature toggles instead.
POST: http://unleash.host.com/api/admin/features/:featureName/toggle/off
Used to disable a feature toggle. The :featureName must match an existing Feature Toggle. Returns 200-response if the feature toggle was disabled successfully.
Body
None
Example response:
{
"name": "Feature.A",
"description": "lorem ipsum..",
"type": "release",
"enabled": false,
"stale": false,
"strategies": [
{
"name": "default",
"parameters": {}
}
],
"variants": [],
"tags": []
}
Mark a Feature Toggle as "stale"
This endpoint was removed in v5. Please use the project-based endpoint to patch a feature toggle and mark it as stale instead.
POST: http://unleash.host.com/api/admin/features/:featureName/stale/on
Used to mark a feature toggle as stale (deprecated). The :featureName must match an existing Feature Toggle. Returns 200-response if the feature toggle was enabled successfully.
Body
None
Example response:
{
"name": "Feature.A",
"description": "lorem ipsum..",
"type": "release",
"enabled": true,
"stale": true,
"strategies": [
{
"name": "default",
"parameters": {}
}
],
"variants": [],
"tags": []
}
Mark a Feature Toggle as "active"
This endpoint was removed in v5. Please use the project-based endpoint to patch a feature toggle and mark it as not stale instead.
POST: http://unleash.host.com/api/admin/features/:featureName/stale/off
Used to mark a feature toggle active (remove stale marking). The :featureName must match an existing Feature Toggle. Returns 200-response if the feature toggle was disabled successfully.
Body
None
Example response:
{
"name": "Feature.A",
"description": "lorem ipsum..",
"type": "release",
"enabled": false,
"stale": false,
"strategies": [
{
"name": "default",
"parameters": {}
}
],
"variants": [],
"tags": []
}