Retrieve list of executions with filters, pagination, and optional inclusion of job details.
Request
Query parameters
| Key | Required | Type | Description |
|---|---|---|---|
| filter | No | string |
Filter the results by specifying one or more filters. Filter operators:
By default, multiple filter expressions are combined in an AND expression. Filter expressions can be grouped by appending the optional group For example, these filter expressions are in two different groups (0 and 1), so the combined expressions return results where
Filter expressions are case insensitive by default. |
| sort | No | string |
Sort the results by a field in ascending or descending order Specify Example: To first sort by
field1 in ascending order and then by field2 in descending order, use two sort expressions: |
| offset | No | number |
The number of records to skip before returning results. The minimum is |
| limit | No | number | The number of records to return per page. The minimum is 1 |
| includeTotal | No | boolean |
Return a count of the total number of records that match the specified filter expression regardless of the number of number of records returned in the response page.
The count is returned by the total property in the response body. If the totalOverflow property is set to true in the response body, then the total count is an estimate that may exceed the actual number of records returned by the search. If not |
| includeJobs | No | boolean |
Response
Response body properties
| Ancestors | Property | Required | Type | Description |
|---|---|---|---|---|
| data | array(object) | Data envelope for response. | ||
| data | stages | No | array | |
| data | errors | No | array | |
| data | jobs | No | array | |
| data | id | No | string |
|
| data | type | No | string | |
| data | properties | No | ||
| data | status | No | string |
This property is an enumerated string type (enum) set to one of these values:
|
| data | createdBy | No | string | |
| data | createdAt | No | string |
|
| data | updatedAt | No | string |
|
| data | startedAt | No | string |
|
| data | completedAt | No | string |
|
Response examples
Example status code responses for this method are shown here.
"data": {
"id":"694aba23acba98e2bba07a42",
"type": "template-deploys",
"stages": [
{
"total": "1",
"processed": "1",
"errors": "0"
}
]
"status": "completed",
"createdBy": "0oa2bhgeshd008aOT0h8",
"createdAt": "2025-12-23T15:49:55.455Z",
"updatedAt": "2025-12-23T22:38:39.474Z",
"startedAt": "2025-12-23T15:50:27.432Z",
"completedAt": "2025-12-23T22:38:39.474Z"
}
"links": {
"self": "https://api.cloud.precisely.com/executions"
}
"value": {
"statusCode": "400",
"error": "Bad Request",
"message": "Bad Request"
}
"value": {
"statusCode": "401",
"error": "Unauthorized",
"message": "Authentication required"
}
"value": {
"statusCode": "404",
"error": "Not Found",
"message": "Resource not found"
}
"value": {
"statusCode": "429",
"error": "Too Many Requests",
"message": "Rate limit exceeded"
}
"value": {
"statusCode": "500",
"error": "Internal Server Error",
"message": "An unexpected error occurred"
}
"value": {
"statusCode": "503",
"error": "Service Unavailable",
"message": "Service temporarily unavailable"
}
"value": {
"statusCode": "504",
"error": "Gateway Timeout",
"message": "Request timeout"
}