| GET | /featuretoggles/{id} | Get details for a specified FeatureToggle |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | path | Guid | Yes | The FeatureToggle Id. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Info | form | FeatureToggleInfo | No | |
| IncludedUsers | form | List<FeatureToggleUser> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | Guid | No | |
| Key | form | string | No | |
| LinkedIssue | form | string | No | |
| Description | form | string | No | |
| CreatedById | form | Guid | No | |
| CreatedByUserName | form | string | No | |
| DateCreated | form | DateTime | No | |
| Status | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | Guid | No | |
| UserName | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /featuretoggles/{id} HTTP/1.1
Host: api.paylock.com
Accept: text/jsv
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
info:
{
id: 00000000000000000000000000000000,
key: String,
linkedIssue: String,
description: String,
createdById: 00000000000000000000000000000000,
createdByUserName: String,
dateCreated: 0001-01-01,
status: String
},
includedUsers:
[
{
id: 00000000000000000000000000000000,
userName: String
}
]
}