Get Execution Alert Status
Endpoint Information
- URL: {gateway-url}/alerts/status/type/execution
- Method: GET
- Authentication: Required (Bearer Token)
- Company Header: Required (X-Company-Id)
Headers
Header | Type | Required | Description |
|---|---|---|---|
Authorization | String | Yes | Bearer token used for authentication. Example: Bearer <your_access_token>. |
X-Company-Id | Long | Yes | The company ID used to scope the request. |
Accept | String | No | Recommended value: application/json. |
Request Body
This endpoint does not require a request body.
Response Body
{
"data": [
{
"name": "EXECUTION_STARTED",
"description": "Beginning of the Each Execution",
"multiSelect": false
},
{
"name": "EXECUTION_COMPLETED",
"description": "End of the Each Execution",
"multiSelect": true
}
]
}Response Fields
Parameter | Type | Description |
|---|---|---|
data | Array of objects | List of execution-level alert statuses. |
data[].name | String | Internal status name used by the API. |
data[].description | String | Display value of the alert status. This value is used while creating an alert. |
data[].multiSelect | Boolean | Indicates whether multiple result statuses can be selected for this execution alert status. |
Behavior Notes
- EXECUTION_STARTED represents alerts triggered at the beginning of each execution.
- EXECUTION_COMPLETED represents alerts triggered at the end of each execution.
- When multiSelect is true, related result alert statuses can be selected by using the result alert status endpoint.
- The response does not include result.code or result.message.
Error Response Format
Error responses use the common problem detail format.
{
"instance": "/alerts/status/type/execution",
"status": 401,
"title": "Unauthorized",
"type": "https://errors.testinium.com/exception",
"timestamp": "2026-08-18T12:08:41.165927056Z",
"errorType": "EXCEPTION",
"errors": {
"code": 10001,
"message": "Full authentication is required to access this resource"
}
}Error Codes
HTTP Code | Error Message | Description |
|---|---|---|
400 | BAD_REQUEST | The request is malformed or a required header is missing. |
401 | UNAUTHORIZED | Authentication failed, authentication is required, or the token is invalid. |
403 | FORBIDDEN | The user does not have permission to access the requested company or resource. |
500 | INTERNAL_SERVER_ERROR | An unexpected error occurred on the server side. |
Application Error Codes
Code | Error Type | HTTP Code | Description |
|---|---|---|---|
10000 | EXCEPTION | 401 | Authentication failed. |
10001 | EXCEPTION | 401 | Authentication is required to access this resource. |
10002 | EXCEPTION | 401 | The provided token is invalid. |
10003 | EXCEPTION | 403 | The user is not authorized for the requested resource. |
10004 | EXCEPTION | 400 | A required header is missing. For example, X-Company-Id is not provided. |
10005 | EXCEPTION | 400 | A required token claim is missing. |
10007 | EXCEPTION | 403 | The user does not have access to the requested resource. |
10008 | EXCEPTION | 500 | The routed notification service is unavailable. |
Example Request
curl --location '{gateway-url}/alerts/status/type/execution' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <your_access_token>' \
--header 'X-Company-Id: <company_id>'