Querying Historical Alarms

Function

This API is used to query historical alarms by alarm ID.

Authorization Information

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.

If you are using identity policy-based authorization, the following identity policy-based permissions are required.

Action	Access Level	Resource Type (*: required)	Condition Key	Alias	Dependencies
coc:alarm:listHandleHistories	List	-	-	-	-

URI

GET /v1/alarm-mgmt/alarm/{alarm_id}/handle-histories

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
alarm_id	Yes	String	Definition: Alarm ID, which uniquely identifies an alarm. You can obtain the alarm ID from the aggregated alarms page of the alarm management module on COC. Constraints: N/A Value range: 0–26 characters, starting with ALM. Default value: N/A

**Table 2** Query Parameters
Parameter	Mandatory	Type	Description
offset	Yes	Integer	Definition: Offset pointers queried by page. Constraints: N/A Value range: N/A Default value: N/A
limit	Yes	Integer	Definition: Number of queried results, by page. Constraints: N/A Value range: N/A Default value: N/A

Request Parameters

None

Response Parameters

Status code: 200

**Table 3** Response body parameters
Parameter	Type	Description
count	Long	Definition: Number of service tickets executed for the historical alarms. An alarm ticket can be executed multiple times. Each execution record is bound to the alarm ticket for users to query. Constraints: N/A Value range: N/A Default value: N/A
alarm_handle_histories	Array of AlarmHandleHistory objects	Definition: Execution details of the service tickets of the historical alarms. Constraints: N/A Value range: N/A Default value: N/A

**Table 4** AlarmHandleHistory
Parameter	Type	Description
work_order_id	String	Definition: ID of the task execution service ticket. You can switch to the service ticket tab page to query the service ticket information of the corresponding task type on the Task Management > Execution Records page of COC. Constraints: N/A Value range: N/A Default value: N/A
create_name	String	Definition: Name of the service ticket creator. Constraints: N/A Value range: N/A Default value: N/A
create_alias	String	Definition: Alias of the service ticket creator. Constraints: N/A Value range: N/A Default value: N/A
task_type	String	Definition: Service ticket task type. Constraints: N/A Value range: SCRIPT: script RUNBOOK: job Default value: N/A
start_time	Long	Definition: Start time of service ticket execution. Constraints: N/A Value range: N/A Default value: N/A
end_time	Long	Definition: End time of service ticket execution. Constraints: N/A Value range: N/A Default value: N/A
duration	Long	Definition: Time required for executing a service ticket. Constraints: N/A Value range: N/A Default value: N/A
status	String	Definition: Service ticket status. Constraints: N/A Value range: N/A Default value: N/A

Example Requests

Query the historical alarm whose ID is ALM2025071216523205dS85AL9.

GET https://{Endpoint}/v1/alarm-mgmt/alarm/ALM2025071216523205dS85AL9/handle-histories?offset=0&limit=10

{ }

Example Responses

Status code: 200

Response is returned correctly.

{
  "alarm_handle_histories" : {
    "associated_task_id" : "SC20250422142607018c62b2d",
    "associated_task_name" : "Platform dialing test automation",
    "create_name" : "COC_TEST",
    "duration" : 448,
    "end_time" : 1752484954398,
    "start_time" : 1752484949914,
    "status" : "FINISHED",
    "task_type" : "SCRIPT",
    "work_order_id" : "SCT20250714172229018ca2ef9"
  },
  "count" : 1
}