Queries tests.
Debugging
Request headers
This operation uses only the common request headers. For more information, see Common request parameters.
Request syntax
GET /v4/openapi/app-groups/[appGroupIdentity]/scenes/[sceneId]/groups/[groupId]/experiments HTTP/1.1
Request parameters
Parameter | Type | Position | Required | Example | Description |
---|---|---|---|---|---|
appGroupIdentity | String | Path | Yes | "my_app_group_name" |
The name of the application. |
groupId | Integer | Path | Yes | 20404 |
The ID of the test group. |
sceneId | Integer | Path | Yes | 13467 |
The ID of the test scenario. |
Response parameters
Parameter | Type | Example | Description |
---|---|---|---|
requestId | String | D77D0DAF-790D-F5F5-A9C0-133738165014 |
The ID of the request. |
result | Array of result |
The details of the tests. For more information, see ABTestExperiment. |
|
created | Integer | 1588842080 |
The time when the test was created. |
id | String | 12888 |
The ID of the test group. |
name | String | test1 |
The name of the test group. |
online | Boolean | true |
The status of the test. Valid values:
|
params | Map | 1 |
The parameters of the test. |
traffic | Integer | 30 |
The percentage of traffic that is routed to the test. Valid values: [0,100]. |
updated | Integer | 1588842080 |
The time when the test was last modified. |
Examples
Sample requests
GET /v4/openapi/app-groups/my_app_group_name/scenes/20404/groups/13466/experiments
Sample success responses
XML
format
<requestId>D77D0DAF-790D-F5F5-A9C0-133738165014</requestId>
<result>
<id>12888</id>
<name>test1</name>
<params>
<firstFormulaName>default</firstFormulaName>
</params>
<created>1588842080</created>
<updated>1588842080</updated>
<online>true</online>
<traffic>30</traffic>
</result>
JSON
format
{
"requestId": "D77D0DAF-790D-F5F5-A9C0-133738165014",
"result": [
{
"id": "12888",
"name": "test1",
"params": {
"firstFormulaName": "default"
},
"created": 1588842080,
"updated": 1588842080,
"online": true,
"traffic": 30
}
]
}
Error codes
For a list of error codes, visit the API Error Center.