Modifying the Cold Storage Scope of a Media Asset

Modifies the cold storage scope of a media asset.

By default, cold storage applies to the source and output media files. You can also apply cold storage only to the source media file.

PUT /v1/{project_id}/asset/storage-mode-type

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details about how to obtain the project ID, see Obtaining a Project ID.

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	No	String	User token. This parameter is mandatory when token authentication is used. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is a token.
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.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
storage_mode_type	No	String	Cold storage mode. Options: WHOLE: Cold storage applies to both the source and transcoded media files. ORIGIN: Cold storage applies only to the source media file.

Status code: 400

**Table 4** Response body parameters
Parameter	Type	Description
error_code	String	Error code
error_msg	String	Error description

Modify the cold storage scope of a media asset.

PUT https://{endpoint}/v1/{project_id}/asset/storage-mode-type

Content-Type: application/json
{
  "storage_mode_type": "ORIGIN"
}

Status code: 400

The information is returned when the request failed.

{
  "error_code" : "VOD.10053",
  "error_msg" : "The request parameter is illegal, illegal field: {xx}."
}

Status Code	Description
204	The information is returned when the request succeeded.
400	The information is returned when the request failed.

Parent topic: Media Asset Storage Mode Management

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.