Queries stream ingest callback records.
Operation description
You can call this operation up to 100 times per second per account. Requests that exceed this limit are dropped and you will experience service interruptions. We recommend that you take note of this limit when you call this operation.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
live:DescribeLiveStreamsNotifyRecords | get | *Domain acs:cdn:*:{#accountId}:domain/{#DomainName} |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
DomainName | string | Yes | The ingest domain. | push.example1.com |
AppName | string | No | The name of the application to which the live stream belongs. You can view the application name on the Stream Management page of the ApsaraVideo Live console. | app |
StreamName | string | No | The name of the live stream. You can view the stream name on the Stream Management page of the ApsaraVideo Live console. | stream |
Status | string | No | Specifies whether to return the records of successful or failed callbacks. Valid values:
| success |
StartTime | string | Yes | The beginning of the time range to query. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC. Note
The start time must be in the last seven days.
| 2017-12-10T08:00:00Z |
EndTime | string | Yes | The end of the time range to query. The end time must be later than the start time. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC. | 2017-12-10T09:00:00Z |
PageSize | integer | No | The number of entries per page. Default value: 20. Maximum value: 500. Valid values: integers from 1 to 500. | 20 |
PageNumber | integer | No | The page number. Default value: 1. | 1 |
Response parameters
Examples
Sample success responses
JSON
format
{
"NotifyRecordsInfo": {
"LiveStreamNotifyRecordsInfo": [
{
"AppName": "app",
"Description": "success",
"DomainName": "push.example1.com",
"NotifyContent": "{\\\"action\\\":\\\"publish_done\\\",\\\"app\\\":\\\"push.example1.com\\\"}",
"NotifyResult": "success",
"NotifyTime": "2022-10-19T19:09:28Z",
"NotifyType": "publish_done",
"NotifyUrl": "http://xx.xx.xx.xx/callbacks",
"StreamName": "stream"
}
]
},
"PageNum": 1,
"PageSize": 20,
"RequestId": "F675E4B4-125D-1533-901B-11A724644285",
"TotalNum": 20,
"TotalPage": 20
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidStartTime.Malformed | Specified parameter StartTime is not valid. | - |
400 | InvalidEndTime.Malformed | Specified parameter EndTime is not valid. | - |
400 | InvalidParam | Parameter invalid. | Illegal input parameters |
400 | InvalidEndTime.Mismatch | Specified EndTime does not match the specified StartTime. | - |
400 | Duration.Exceed | StartTime needs to be within the last 7 days. | - |
500 | InternalError | The request processing has failed due to backend service exception. | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-03-14 | The Error code has changed | View Change Details |