tencent cloud

Feature Description

CI supports user-defined callback URLs. After a task is completed, the system sends an HTTP POST request whose body contains notification content to a user-defined callback URL. You can use the configured callback URL to learn about the processing progress and status of the task so that you can perform other operations as needed.

Callback Content

After the task is completed, the system sends the callback content to the callback URL that you configure. The response body is returned as application/xml data. The following contains all the nodes:

<Response>
     <JobsDetail>
         <Code></Code>
         <Message></Message>
         <JobId></JobId>
         <State></State>
         <CreationTime></CreationTime>
         <EndTime></EndTime>
         <QueueId></QueueId>
         <Tag></Tag>
         <Input>
               <CosHeaders></CosHeaders>
               <Region></Region>
               <BucketId></BucketId>
               <Object></Object>
         </Input>
         <Operation>
               <TemplateId></TemplateId>
               <TemplateName></TemplateName>
               <MediaResult></MediaResult>
               <Output>
                  <Region></Region>
                  <Bucket></Bucket>
                  <Object></Object>
               </Output>
               <MediaInfo>
               </MeidaInfo>
         </Operation>
         <Workflow>   
               <RunId></RunId>   
               <WorkflowId></WorkflowId>  
               <WorkflowName></WorkflowName>  
               <Name></Name>
         </Workflow>
     </JobsDetail>
</Response>

The nodes are described as follows:

Response has the following sub-nodes:

JobsDetail has the following sub-nodes:

Input has the following sub-nodes:

CosHeaders has the following sub-nodes:

Operation has the following sub-nodes:

Output has the following sub-nodes:

MediaResult has the following sub-nodes:

OutputFile has the following sub-nodes:

Note：

The actual output file is the StringConcat(ObjectPrefix,ObjectName) file in the bucket specified by Bucket in the region specified by Region.

Workflow has the following sub-nodes:

MediaInfo has the following sub-nodes:
Same as the Response.MediaInfo node in the GenerateMediaInfo API.

Examples

<Response>
  <JobsDetail>
      <Code>Success</Code>
      <CreationTime>2020-11-16T16:43:29+0800</CreationTime>
      <EndTime>2020-11-16T16:43:33+0800</EndTime>
      <Input>
          <CosHeaders>
              <Key>x-cos-meta-test</Key>
              <Value>testvalue</Value>
          </CosHeaders>
          <CosHeaders>
              <Key>x-cos-meta-name</Key>
              <Value>xxxxxx</Value>
          </CosHeaders>
          <CosHeaders>
              <Key>x-cos-meta-age</Key>
              <Value>10</Value>
          </CosHeaders>
          <Object>1/2/3/4/5/xxx.mp4</Object>
          <Region>ap-beijing</Region>
          <BucketId>examplebucket-1250000000</BucketId>
      </Input>
      <JobId>jccddc41c27e711ebbff5874bc5b36868</JobId>
      <Message/>
      <Operation>
          <MediaResult>
              <OutputFile>
                  <Bucket>examplebucket-1250000000</Bucket>
                  <ObjectName>1/2/Conversion to mp4-xxx_iccba81fa27e711eb989d525400276c76.mp4</ObjectName>
                  <ObjectPrefix/>
                  <Region>ap-chongqing</Region>
              </OutputFile>
          </MediaResult>
          <Output>
              <Bucket>examplebucket-1250000000</Bucket>
              <Object>1/2/Conversion to mp4-xxx_iccba81fa27e711eb989d525400276c76.${ext}</Object>
              <Region>ap-chongqing</Region>
          </Output>
          <TemplateId>t182c0ca7d91ca40969a3fc97c5559091a</TemplateId>
          <TemplateName>example</TemplateName>
      </Operation>
      <Workflow>   
          <RunId>rccddc41c27e711ebbff5874bc5b36868</RunId>   
          <WorkflowId>wccddc41c27e711ebbff5874bc5b36868</WorkflowId>  
          <WorkflowName>workflow</WorkflowName>  
          <Name>Transcode_1600413767444</Name>
      </Workflow>
      <QueueId>p791b0bca54ee44289f0d4b1d90796c4f</QueueId>
      <State>Success</State>
      <Tag>Transcode</Tag>
  </JobsDetail>
</Response>