tencent cloud

Feedback

Updating a Media Processing Queue

Last updated: 2021-12-31 17:20:38

    Feature Description

    This API (UpdateMediaQueue) is used to update a media processing queue.

    Request

    Sample request

    PUT /queue/p8eb46b8cc1a94bc09512d16c5c4f4d3a HTTP/1.1
    Host: <BucketName-APPID>.ci.<Region>.myqcloud.com
    Date: <GMT Date>
    Authorization: <Auth String>
    Content-Length: <length>
    Content-Type: application/xml
    <body>
    
    Note:

    Authorization: Auth String (For more information, please see Request Signature.)

    Request headers

    This API only uses Common Request Headers.

    Request body

    This request requires the following request body:

    <Request>
      <Name>Queue Name</Name>
      <QueueID></QueueID>
      <State></State>
      <NotifyConfig>
          <Type></Type>
          <Url></Url>
          <Event></Event>
      </NotifyConfig>
    </Request>
    

    The nodes are described as follows:

    Node Name (Keyword) Parent Node Description Type Required
    Request None Request container Container Yes

    Request has the following sub-nodes:

    Node Name (Keyword) Parent Node Description Type Required Constraints
    Name Request Template Name String Yes Length limit: 100 characters
    QueueID Request Channel ID String Yes -
    State Request Channel status String Yes 1. Active: jobs in the channel will be scheduled and transcoded by the media transcoding service.
    2. Paused: the channel is paused, and jobs in the channel will no longer be scheduled and transcoding. All jobs in the channel remain in the submitted state, and the tasks being transcoded will continue to be transcoded without being affected.
    NotifyConfig Request Notification channel Container Yes Third-party callback URL

    NotifyConfig has the following sub-nodes:

    Node Name (Keyword) Parent Node Description Type Required Constraints
    Url Request.NotifyConfig Callback configuration String No Length limit: 100 characters
    Type Request.NotifyConfig Callback type, normal callback: URL String No Length limit: 100 characters
    Event Request.NotifyConfig Task completed: TaskFinish; workflow completed: WorkflowFinish String No Length limit: 100 characters
    State Request.NotifyConfig Callback switch: Off, On String No Length limit: 100 characters

    Response

    Response headers

    This API only returns Common Response Headers.

    Response body

    The response body returns application/xml data. The following contains all the nodes:

    <Response>
      <RequestId>NTk0MjdmODlfMjQ4OGY3XzYzYzhf****</RequestId>
      <Queue>
          <QueueId></QueueId>
          <Name></Name>
          <State>Active</State>
          <NotifyConfig>
              <Url>mts-topic-1</Url>
              <Type></Type>
              <Event></Event>
          </NotifyConfig>
          <CreateTime></CreateTime>
          <UpdateTime></UpdateTime>
      </Queue>
    </Response>
    

    The nodes are described as follows:

    Node Name (Keyword) Parent Node Description Type
    Response None Response container Container

    Response has the following sub-nodes:

    Node Name (Keyword) Parent Node Description Type
    RequestId Response Unique ID of the request String
    Queue Response Queue information. Same as Response.QueueList in DescribeMediaQueues. Container

    Error codes

    No special error message will be returned for this request. For the common error messages, please see Error Codes.

    Examples

    Request

    PUT /queue/p8eb46b8cc1a94bc09512d16c5c4f4d3a HTTP/1.1
    Authorization: q-sign-algorithm=sha1&q-ak=AKIDZfbOAo7cllgPvF9cXFrJD0a1ICvR****&q-sign-time=1497530202;1497610202&q-key-time=1497530202;1497610202&q-header-list=&q-url-param-list=&q-signature=28e9a4986df11bed0255e97ff90500557e0e****
    Host: examplebucket-1250000000.ci.ap-beijing.myqcloud.com
    Content-Length: 1666
    Content-Type: application/xml
    <Request>
      <Name>Queue Name</Name>
      <QueueID></QueueID>
      <State></State>
      <NotifyConfig>
          <Type></Type>
          <Url></Url>
          <Event></Event>
      </NotifyConfig>
    </Request>
    

    Response

    HTTP/1.1 200 OK
    Content-Type: application/xml
    Content-Length: 100
    Connection: keep-alive
    Date: Thu, 15 Jun 2017 12:37:29 GMT
    Server: tencent-ci
    x-ci-request-id: NTk0MjdmODlfMjQ4OGY3XzYzYzhf****
    <Response>
      <RequestId>NTk0MjdmODlfMjQ4OGY3XzYzYzhf****</RequestId>
      <Queue>
          <QueueID></QueueID>
          <Name></Name>
          <State>Active</State>
          <NotifyConfig>
              <Type></Type>
              <Url></Url>
              <Event></Event>
          </NotifyConfig>
          <CreateTime></CreateTime>
          <UpdateTime></UpdateTime>
      </Queue>
    </Response>
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support