9.6.1 Acquisition of a list of tasks
Function
Acquires a list of tasks.
Execution permissions
Admin role, Develop role, Modify role, Submit role
API version
v1
Request format
GET http://host:port/Automation/version/objects/Tasks
This API acquires a list of all tasks for which the user who executed the API has permissions. By specifying query parameters, you can filter the tasks for which you want to acquire the list. Specify query parameters in the following format.
?query-parameter=value[&query-parameter=value...]
|
Query parameter |
Filter condition |
|---|---|
|
serviceID |
Equal to the specified value |
|
scheduleID |
Equal to the specified value |
For details about other query parameters that can be specified, see 9.2.9 Query parameter.
- Example
-
The following example specifies 2015 for serviceID as a query parameter.
?serviceID=2015
Status code
The following table describes the various status codes that can be returned as the response to a request.
|
Status code |
Message |
Description |
|---|---|---|
|
200 |
OK |
Processing has been successfully completed. |
|
400 |
Bad Request |
The query parameter is invalid. |
|
401 |
Unauthorized |
The user does not have login permission. |
|
412 |
Precondition failed |
The server is not available. |
|
500 |
Server-side error |
A server processing error occurred. |
Response schema
Data that matches the conditions specified by query parameters in a request is returned in the response body. The following shows the schema of the response body.
{
"data" : [ {"member-of-a-resource-for-task-functionality(Tasks)" : value ... }, ... ],
"count" : number-of-data-items-that-match-the-conditions-specified-by-query-parameters(0-to-n)
}Usage example
In the following example, the API acquires a list of all tasks.
Request header:
GET /Automation/v1/objects/Tasks HTTP/1.1
Host:10.196.184.238:22015
Accept:application/json
Accept-Language: ja
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: useragent1
Response header:
HTTP/1.1 200 OK
Date: Mon, 14 Jul 2014 11:47:45 GMT
Server: Cosminexus HTTP Server
Access-Control-Expose-Headers: WWW-Authenticate
WWW-Authenticate: HSSO bd804a4bbfb57c37cad7fe56034d49e428b615_V0300
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, DELETE, PUT, HEAD, OPTIONS
Access-Control-Allow-Credentials: true
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: application/json
Response body:
{
"data" : [ {
"instanceID" : 2026,
"name" : "testService1_20140714044426",
"status" : "completed",
"startTime" : "2014-07-14T04:45:35.000-0700",
"endTime" : "2014-07-14T04:45:35.000-0700",
"submitter" : "System",
"submitTime" : "2014-07-14T04:45:34.000-0700",
"modifyTime" : "2014-07-14T04:45:57.000-0700",
"serviceState" : "release",
"scheduleID" : 2025,
"serviceGroupID" : 3,
"serviceID" : 2015
} ],
"count" : 1
}
Related topic