tencent cloud

Submitting Tasks
Last updated: 2025-11-19 15:32:21
Submitting Tasks
Last updated: 2025-11-19 15:32:21

Feature Description

Submit an audio and video stream separation task.

Authorization Description

When used by a sub-account, the ci:CreateMediaJobs permission is required. For details, see Cloud Infinite action.
When a sub-account uses an asynchronous processing interface, the cam:passrole permission is required. The asynchronous processing interface performs read and write operations on COS resources through the "role" in CAM. The PassRole permission is used for role passing. For details, refer to Access Management > Write Operation > PassRole API.

Service Activation

To use this feature, you need to enable Cloud Infinite in advance and bind a bucket. For details, see Bind Bucket.
Use this feature requires enabling Media Processing Service in advance via console or API. For details, see Enable Media Processing Service.

Use Limits

When using this API, please first confirm the relevant restrictions. For details, see Usage Limits.

Fee Description

This API is a paid service. Incurred fees will be collected by Cloud Infinite. For detailed billing instructions, see Media processing.


Request

Request sample:

POST /jobs HTTP/1.1
Host: <BucketName-APPID>.ci.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
Content-Length: <length>
Content-Type: application/xml

<body>
Description
Authorization: Auth String. For details, see Request Signature document.

Request header.

This API only uses common request headers. For details, see Common Request Headers documentation.

Request body.

The implementation of this request operation requires the following request body.
<Request>
<Tag>StreamExtract</Tag>
<Input>
<Object>input/demo.mp4</Object>
</Input>
<Operation>
<Output>
<Region>ap-chongqing</Region>
<Bucket>test-123456789</Bucket>
<StreamExtract>
<Index>0</Index>
<Object>output/out0.mp4</Object>
</StreamExtract>
<StreamExtract>
<Index>1</Index>
<Object>output/out1.mp4</Object>
</StreamExtract>
<UserData>This is my data.</UserData>
<JobLevel>0</JobLevel>
</Output>
</Operation>
<CallBack>http://callback.demo.com</CallBack>
<CallBackFormat>JSON</CallBackFormat>
</Request>
The data are described as follows:
Node Name (Keyword)
Parent Node
Description
Type
Required or Not
Request
None.
Container for saving requests
Container
Yes
The specific data description of the Container type Request is as follows:
Node Name (Keyword)
Parent Node
Description
Type
Required or Not
Tag
Request
Tag for creating a task: StreamExtract
String
Yes
Input
Request
File information to be operated
Container
Yes
Operation
Request
Operation rule
Container
Yes
CallBackFormat
Request
Job callback format, JSON or XML, default XML, priority is higher than the callback format of the queue
String
No
CallBackType
Request
Job callback type, Url or TDMQ, default Url, priority is higher than the callback type of the queue
String
No
CallBack
Request
job callback address, priority is higher than the callback address of the queue. When set to no, it indicates that the callback address of the queue does not generate a callback.
String
No
CallBackMqConfig
Request
task callback TDMQ configuration, required when CallBackType is TDMQ. For details, see CallBackMqConfig.
Container
No
The specific data description of the Container type Input is as follows:
Node Name (Keyword)
Parent Node
Description
Type
Required or Not
Object
Request.Input
file path
String
Yes
The specific data description of the Container type
Operation
is as follows:
Node Name (Keyword)
Parent Node
Description
Type
Required or Not
Output
Request.Operation
Output configuration
Container
Yes
UserData
Request.Operation
Pass through user information, printable ASCII code, length not exceeding 1024
String
No
JobLevel
Request.Operation
Task priority, level limit: 0, 1, 2. Higher levels indicate higher task priority, default is 0.
String
No
The specific data description of the Container type Output is as follows:
Node Name (Keyword)
Parent Node
Description
Type
Required or Not
Region
Request.Operation.Output
Region of the storage bucket
String
Yes
Bucket
Request.Operation.Output
Bucket for storing results
String
Yes
StreamExtract
Request.Operation.Output
Result file configuration information, supports up to 10 stream configurations
Container array
Yes
The specific data description of the Container type StreamExtract is as follows:
Node Name (Keyword)
Parent Node
Description
Type
Required or Not
Index
Request.Operation.Output.StreamExtract
Stream number, corresponding to Response.MediaInfo.Stream in media information
Video.Index and Response.MediaInfo.Stream.Audio.Index. For details, refer to get media information interface. When the input media format is mxf, only Video Stream extraction is supported.
String
Yes
Object
Request.Operation.Output.StreamExtract
Result output filename.
String
Yes

Response

Response Headers

This API only returns the public response header. For details, see Common Response Headers documentation.

Response Body

The response body is returned as application/xml. An example including the complete node data is shown below:
<Response>
<JobsDetail>
<Code>Success</Code>
<Message/>
<JobId>j8d121820f5e411ec926ef19d53ba9c6f</JobId>
<State>Submitted</State>
<CreationTime>2022-06-27T15:23:11+0800</CreationTime>
<StartTime>-</StartTime>
<EndTime>-</EndTime>
<QueueId>p2242ab62c7c94486915508540933a2c6</QueueId>
<Tag>StreamExtract</Tag>
<Input>
<BucketId>test-123456789</BucketId>
<Object>input/demo.mp4</Object>
<Region>ap-chongqing</Region>
</Input>
<Operation>
<Output>
<Bucket>test-123456789</Bucket>
<Region>ap-chongqing</Region>
<StreamExtract>
<Index>0</Index>
<Output>output/out0.mp4</Output>
</StreamExtract>
<StreamExtract>
<Index>1</Index>
<Output>output/out1.mp4</Output>
</StreamExtract>
</Output>
<UserData>This is my data.</UserData>
<JobLevel>0</JobLevel>
</Operation>
</JobsDetail>
</Response>
The data are as follows:
Node Name (Keyword)
Parent Node
Description
Type
Response
None.
Container for saving results
Container
Container node Response content:
Node Name (Keyword)
Parent Node
Description
Type
JobsDetail
Response
Task details
Container array
Content of Container node
JobsDetail
:
Node Name (Keyword)
Parent Node
Description
Type
Code
Response.JobsDetail
error code, meaningful only when State is Failed
String
Message
Response.JobsDetail
error description, meaningful only when State is Failed
String
JobId
Response.JobsDetail
ID of the newly created task
String
Tag
Response.JobsDetail
Tag for the newly created task: StreamExtract
String
State
Response.JobsDetail
Task Status
Submitted: submitted, pending execution
Running: executing
Success: execution successful
Failed: execution failed
Pause: Task is paused. When the pause queue is activated, to-be-executed tasks become paused state.
Cancel: task cancelled
String
CreationTime
Response.JobsDetail
Task Creation Time
String
StartTime
Response.JobsDetail
Task Start Time
String
EndTime
Response.JobsDetail
Task End Time
String
QueueId
Response.JobsDetail
Task's Queue ID
String
Input
Response.JobsDetail
Input resource address of the task
Container
Operation
Response.JobsDetail
Rules of the task
Container
Contents of the Container node Input:
Node Name (Keyword)
Parent Node
Description
Type
Region
Response.JobsDetail.Input
Region of the storage bucket
String
Bucket
Response.JobsDetail.Input
Bucket for storing results
String
Object
Response.JobsDetail.Input
Output result filename
String
Contents of the Container node Operation:
Node Name (Keyword)
Parent Node
Description
Type
Output
Response.JobsDetail.Operation
In-progress Request's Operation.Output
Container
MediaResult
Response.JobsDetail.Operation
Basic information of the output file. Do not return if the task is incomplete. For details, see MediaResult.
Container
UserData
Response.JobsDetail.Operation
Pass through user information
String
JobLevel
Response.JobsDetail.Operation
Task Priority
String

Error Codes

This request returns common error responses and error codes. For more information, see Error Codes.

Examples

Request

POST /jobs HTTP/1.1
Authorization:q-sign-algorithm=sha1&q-ak=**********************************&q-sign-time=1497530202;1497610202&q-key-time=1497530202;1497610202&q-header-list=&q-url-param-list=&q-signature=**************************************
Host:test-1234567890.ci.ap-chongqing.myqcloud.com
Content-Length: 166
Content-Type: application/xml

<Request>
<Tag>StreamExtract</Tag>
<Input>
<Object>input/demo.mp4</Object>
</Input>
<Operation>
<Output>
<Region>ap-chongqing</Region>
<Bucket>test-123456789</Bucket>
<StreamExtract>
<Index>0</Index>
<Object>output/out0.mp4</Object>
</StreamExtract>
<StreamExtract>
<Index>1</Index>
<Object>output/out1.mp4</Object>
</StreamExtract>
<UserData>This is my data.</UserData>
<JobLevel>0</JobLevel>
</Output>
</Operation>
<CallBack>http://callback.demo.com</CallBack>
<CallBackFormat>JSON</CallBackFormat>
</Request>

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 230
Connection: keep-alive
Date: Mon, 28 Jun 2022 15:23:12 GMT
Server: tencent-ci
x-ci-request-id: NjMxMDJhYTNfMThhYTk0MGFfYmU1OV8zZjc=

<Response>
<JobsDetail>
<Code>Success</Code>
<Message/>
<JobId>j8d121820f5e411ec926ef19d53ba9c6f</JobId>
<State>Submitted</State>
<CreationTime>2022-06-27T15:23:11+0800</CreationTime>
<StartTime>-</StartTime>
<EndTime>-</EndTime>
<QueueId>p2242ab62c7c94486915508540933a2c6</QueueId>
<Tag>StreamExtract</Tag>
<Input>
<BucketId>test-123456789</BucketId>
<Object>input/demo.mp4</Object>
<Region>ap-chongqing</Region>
</Input>
<Operation>
<Output>
<Bucket>test-123456789</Bucket>
<Region>ap-chongqing</Region>
<StreamExtract>
<Index>0</Index>
<Output>output/out0.mp4</Output>
</StreamExtract>
<StreamExtract>
<Index>1</Index>
<Output>output/out1.mp4</Output>
</StreamExtract>
</Output>
<UserData>This is my data.</UserData>
<JobLevel>0</JobLevel>
</Operation>
</JobsDetail>
</Response>

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback