Querying All Virtual Human Livestreaming Tasks of a Tenant
Function
Queries all virtual human livestreaming tasks of a tenant.
Calling Method
For details, see Calling APIs.
URI
GET /v1/{project_id}/smart-live-jobs
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details about how to obtain the project ID, see Obtaining a Project ID. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
offset |
No |
Integer |
Offset where the query starts. |
limit |
No |
Integer |
Number of items displayed on each page. |
state |
No |
String |
Task status. By default, all statuses are selected. Multiple statuses can be queried. Use commas (,) to separate them, for example, state=CREATING,PUBLISHED. |
sort_key |
No |
String |
Sorting field. Currently, only create_time is supported. |
sort_dir |
No |
String |
Sorting mode.
asc is used by default. |
create_since |
No |
String |
Filter the records whose creation time is not earlier than the entered time. |
create_until |
No |
String |
Filter the records whose creation time is not later than the entered time. |
room_name |
No |
String |
Fuzzy search by livestreaming room name. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
No |
String |
User token. This parameter is mandatory when token authentication is used. You can obtain the token by calling the IAM API used to obtain a user token. Value of X-Subject-Token in the response header. |
Authorization |
No |
String |
Authentication information. This parameter is mandatory for AK/SK authentication. |
X-Sdk-Date |
No |
String |
Time when the request is sent. This parameter is mandatory for AK/SK authentication. The format is YYYYMMDD'T'HHMMSS'Z'. |
X-Project-Id |
No |
String |
Project ID. This parameter is mandatory for AK/SK authentication. |
X-App-UserId |
No |
String |
Third-party user ID, which does not allow Chinese characters. |
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
X-Request-Id |
String |
Request ID. |
Parameter |
Type |
Description |
---|---|---|
count |
Integer |
Total number of virtual human livestreaming tasks. |
smart_live_jobs |
Array of SmartLiveJob objects |
Virtual human livestreaming task list. |
Parameter |
Type |
Description |
---|---|---|
job_id |
String |
Virtual human livestreaming task ID. |
room_id |
String |
Live room ID. |
room_name |
String |
Live room name. |
state |
String |
Virtual human livestreaming task status.
|
duration |
Float |
Virtual human livestreaming duration, in seconds. |
start_time |
String |
Start time of a virtual human livestreaming task. The format complies with RFC 3339, for example, 2021-01-10T08:43:17Z. |
end_time |
String |
End time of a virtual human livestreaming task. The format complies with RFC 3339, for example, 2021-01-10T08:43:17Z. |
error_info |
ErrorResponse object |
Virtual human livestreaming task error information. |
create_time |
String |
Time when a virtual human livestreaming task is created. The format complies with RFC 3339, for example, 2021-01-10T08:43:17Z. |
lastupdate_time |
String |
Last update time of a virtual human livestreaming task. The format complies with RFC 3339, for example, 2021-01-10T08:43:17Z. |
rtc_room_info |
RTCRoomInfoList object |
RTC room information. |
live_event_report_url |
String |
URL for reporting livestreaming events. Users report their own livestreaming events to this URL to trigger intelligent interaction and automatic reply. |
live_event_callback_config |
LiveEventCallBackConfig object |
Live event callback notification configuration. |
rtc_callback_config |
RTCLiveEventCallBackConfig object |
RTC callback event configuration. Compatible processing. If the configuration is not carried, LIVE_PROGRESS is subscribed by default. |
stream_duration |
Float |
Virtual human livestream push duration, in seconds. |
block_reason |
String |
Information about live room blocking. |
cover_url |
String |
Live room thumbnail URL |
co_streamer_config |
CoStreamerConfig object |
Co-streamer configuration |
live_job_log |
LiveJobLog object |
Livestreaming task records |
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error description. |
Parameter |
Type |
Description |
---|---|---|
app_id |
String |
RTC application ID. |
room_id |
String |
RTC room ID. |
users |
Array of RTCUserInfo objects |
Information about users joining an RTC room. |
Parameter |
Type |
Description |
---|---|---|
user_type |
String |
User type.
|
user_id |
String |
RTC user ID. |
signature |
String |
RTC authentication token. |
ctime |
Long |
Validity period. Timestamp, in seconds. |
Parameter |
Type |
Description |
---|---|---|
live_event_type_callback_url |
String |
Live event callback URL. HTTPS URL, which must contain an authentication string. |
auth_type |
String |
Authentication type.
|
key |
String |
Key |
callback_event_type |
Array of strings |
Live event types in callbacks. Currently, only the following options are supported:
{ "event_type": "SHOOT_SCRIPT_SWITCH", "message":"{\"room_id\":\"26f065244f754b3aa853b649a21aaf66\",\"job_id\":\"e87104f76d7546ce8a46ac6b04c49c3c\",\"scene_script_name\":\"Product 1\",\"shoot_script_sequence_no\":\"2\",\"shoot_script_title\":\"Paragraph 2\"}" } The RTMP_STREAM_STATE_CHANGE callback is defined as follows: { "event_type": "RTMP_STREAM_STATE_CHANGE", "message":"{\"room_id\":\"26f065244f754b3aa853b649a21aaf66\",\"job_id\":\"e87104f76d7546ce8a46ac6b04c49c3c\",\"output_url\":\"rtmp://xxx/xx/xx\",\"stream_key\":\"xxxxx\",\"state\":\"CONNECTED\"}" } The value of state can be CONNECTING, CONNECTED, DISCONNECTED, RECONNECTING, or END. The REPLY_COMMAND_FINISH callback is defined as follows: { "event_type": "REPLY_COMMAND_FINISH", "message":"{\"room_id\":\"26f065244f754b3aa853b649a21aaf66\",\"job_id\":\"e87104f76d7546ce8a46ac6b04c49c3c\",\"reply_id\":\"e87104f76d7546ce8a46ac6b04c49c3c"}" } |
Parameter |
Type |
Description |
---|---|---|
rtc_callback_event_type |
Array of strings |
Live event types in RTC callbacks. Currently, only the following options are supported: LIVE_PROGRESS: live script progress notification REPLY_COMMAND_FINISH: Playback is complete. The callback event structure is defined as follows:
{ "message_type": "live_progress_notify", "data": { "script_name": "Scene 1", "shoot_script_sequence_no": 2, "shoot_script_title": "Greeting", "offset": "247", "reply_id": "e87104f76d7546ce8a46ac6b04c49c3c" } } The REPLY_COMMAND_FINISH callback is defined as follows: { "message_type": "reply_command_finish_notify", "data":"{ "reply_id":"e87104f76d7546ce8a46ac6b04c49c3c" }" } |
Parameter |
Type |
Description |
---|---|---|
voice_config |
VoiceConfig object |
Voice configuration parameter. |
streamer_action |
String |
Behavior of the streamer when the co-streamer speaks.
|
Parameter |
Type |
Description |
---|---|---|
voice_asset_id |
String |
Timbre asset ID. |
speed |
Integer |
Speech speed. The value defaults to 100 and ranges from 50 to 200.
NOTE:
|
pitch |
Integer |
Pitch. The value defaults to 100 and ranges from 50 to 200. |
volume |
Integer |
Volume. The value defaults to 140 and ranges from 90 to 240. |
Parameter |
Type |
Description |
---|---|---|
interaction_records_url |
String |
Live interaction record file address |
Status code: 400
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error description. |
Status code: 401
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error description. |
Status code: 500
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error description. |
Example Requests
GET https://metastudio.cn-north-4.myhuaweicloud.com/v1/70b76xxxxxx34253880af501cdxxxxxx/smart-live-rooms/24bad716-87b1-45e5-8912-6102f7693265/smart-live-jobs
Example Responses
Status code: 200
Succeeded.
{ "count" : 1, "smart_live_jobs" : [ { "job_id" : "26f06524-4f75-4b3a-a853-b649a21aaf66", "state" : "WAITING", "start_time" : "2022-01-18T16:29:36Z", "end_time" : "2022-01-18T16:30:36Z", "duration" : 60 } ] }
Status code: 400
{ "error_code" : "MSS.00000003", "error_msg" : "Invalid parameter" }
Status code: 401
{ "error_code" : "MSS.00000001", "error_msg" : "Unauthorized" }
Status code: 500
{ "error_code" : "MSS.00000004", "error_msg" : "Internal Error" }
Status Codes
Status Code |
Description |
---|---|
200 |
Succeeded. |
400 |
Parameters error, including the error code and its description. |
401 |
Authentication is not performed or fails. |
500 |
Internal service error. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot