UploadMediaByURL - API Reference| Alibaba Cloud Documentation Center

After the media files are uploaded, you can receive an UploadByURLComplete event notification. For more information, see UploadByURLComplete.

You can query the upload status by calling the GetURLUploadInfos operation. For more information, see GetURLUploadInfos.

Note

After an upload job is submitted, the job is asynchronously executed on the cloud. All submitted upload jobs are queued for execution. You can check the job status based on the URL and media file ID that are returned in the event notification.
The UploadMediaByURL operation is suitable for scenarios where you relocate a site with no specific timeliness requirement. Media files are usually uploaded within several hours or days after a job is submitted. If you want to upload media files in real time, we recommend that you use server upload SDKs to upload media files on your on-premises device. For more information, see SDK download.
The UploadMediaByURL operation is available only in the China (Shanghai) region.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters


Parameter	Type	Required	Example	Description
Action	String	Yes	UploadMediaByURL	The operation that you want to perform. Set the value to UploadMediaByURL.
UploadURLs	String	Yes	https://****.mp4	The URL of the source file. The URL must contain a file name extension, for example, mp4 in `https://****.mp4`. If the URL does not contain a file name extension, you can specify one by setting the FileExtension parameter under the UploadMetadatas parameter. If the URL contains a file name extension and the FileExtension parameter is set, the value of the FileExtension parameter is used. For more information about the supported file name extensions, see Overview. URL encoding is required. Separate multiple URLs with commas (,). You can specify a maximum of 20 URLs. Special characters may cause upload failures. Therefore, encode URLs before you separate them with commas (,).
TemplateGroupId	String	No	ca3a8f6e49*****57b65806709586	The ID of the transcoding template group. Log on to the ApsaraVideo VOD console. In the left-side navigation pane, choose Configuration Management > Media Processing > Transcode. On the Transcode page, you can view the ID of the template group. If this parameter is set to a specific value, the specified template group is used for transcoding. You can also set the TemplateGroupId parameter under the UploadMetadatas parameter.
StorageLocation	String	No	outin-bfefbb90a47c******163e1c7426.oss-cn-shanghai.aliyuncs.com	The storage location of the media file. Log on to the ApsaraVideo VOD console. In the left-side navigation pane, choose Configuration Management > Media Management > Storage. On the Storage page, you can view the storage location. If you do not specify the storage location, the default bucket is used.
UploadMetadatas	String	No	[{"SourceURL":"http://test.com/a.mp4","Title":"urlUploadTest"}]	The metadata of the media files to be uploaded. The value is a JSON string. This parameter takes effect only when the value of the SourceURL parameter matches the URL that is specified by the UploadURLs parameter. The JSON-formatted data, such as `[UploadMetadata, UploadMetadata,…]`, must be converted into a JSON string. For more information, see the UploadMetadata section.
UserData	String	No	{"MessageCallback":{"CallbackURL":"http://test.test.com"},"Extend":{"localId":"xxx","test":"www"}}	The custom configurations, including callback configurations and upload acceleration configurations. The value is a JSON string. For more information, see the "UserData" section in Request parameters. Note The callback configurations take effect only when you specify the HTTP callback URL and select the specific callback events in the ApsaraVideo VOD console. To use the upload acceleration feature, submit a ticket to enable this feature. For more information, see Overview.
AppId	String	No	app-****	The ID of the application. Default value: app-1000000. For more information, see Overview.
WorkflowId	String	No	e1e243b4254*****8248197d6f74f9	The ID of the workflow. Note If both the WorkflowId and TemplateGroupId parameters are set, the value of the WorkflowId parameter takes effect. For more information, see Workflows.

UploadMetadata


Parameter	Type	Required	Description
SourceURL	String	Yes	The URL of the source file to be uploaded.
Title	String	Yes	The title of the media file. The title can be up to 128 bytes in length. The value must be encoded in UTF-8.
FileSize	String	No	The size of the media file.
Description	String	No	The description of the media file. The description can be up to 1,024 bytes in length. The value must be encoded in UTF-8.
CoverURL	String	No	The URL of the custom thumbnail of the media file.
CateId	String	No	The category ID of the media file. Log on to the ApsaraVideo VOD console. In the left-side navigation pane, choose Configuration Management > Media Management > Categories. On the Categories page, you can view the category IDs or modify categories.
Tags	String	No	The tag of the media file. Each tag can be up to 32 bytes in length. You can set a maximum of 16 tags. Separate multiple tags with commas (,). The value must be encoded in UTF-8.
TemplateGroupId	String	No	The ID of the transcoding template group. Log on to the ApsaraVideo VOD console. In the left-side navigation pane, choose Configuration Management > Media Processing > Transcode. On the Transcode page, you can view the ID of the template group. If this parameter is set to a specific value, the specified template group is used for transcoding. If both the request parameter TemplateGroupId and the nested parameter TemplateGroupId are set, the value of the nested parameter takes effect.
WorkflowId	String	No	The ID of the workflow. If both the WorkflowId and TemplateGroupId parameters are set, the value of the WorkflowId parameter takes effect. For more information, see Workflows.
FileExtension	String	No	The file name extension of the media file. For more information about the supported file name extensions, see Overview.

Note

Do not include emoticons in the nested parameters, such as Title, Description, and Tags, under the UploadMetadata parameter.
If you use the No Transcoding template group to upload media files, only the media files in the format of MP4, FLV, MP3, or M3U8 can be played. If you want to use ApsaraVideo Player, the version must be 3.1.0 or later.
If the No Transcoding template group is used, only the FileUploadComplete but not the StreamTranscodeComplete event notification is returned after the media file is uploaded.
In addition to the FileUploadComplete and StreamTranscodeComplete event notifications, ApsaraVideo VOD sends an UploadByURLComplete event notification after the media file is uploaded.
If you specify multiple media files at a time, ApsaraVideo VOD sends an event notification for each media file after the media file is uploaded.

Response parameters


Parameter	Type	Example	Description
RequestId	String	25818875-5F78-4A*****F6-D7393642CA58	The ID of the request.
UploadJobs	Array of UploadJob		The information about one or more upload jobs.
JobId	String	ad90a501b1b94*****fb72374ad005046	The ID of the upload job.
SourceURL	String	http://****.mp4	The URL of the source file that is uploaded in the upload job.

Note

This operation is used to asynchronously upload media files. Upload jobs are queued for execution after they are submitted. The completion time of an upload job varies with the number of jobs in the queue.

Examples

Sample requests

https://vod.aliyuncs.com/?Action=UploadMediaByURL
&UploadURLs=https://****.mp4
&<Common request parameters>

Sample success responses

XML format

<UploadMediaByURLResponse>
	  <RequestId>25818875-5F78-4A*****F6-D7393642CA58</RequestId>
	  <UploadJobs>
		    <JobId>ad90a501b1b94*****fb72374ad005046</JobId>
		    <SourceURL>http://****.mp4</SourceURL>
	  </UploadJobs>
</UploadMediaByURLResponse>

JSON format

{
    "RequestId":"25818875-5F78-4A*****F6-D7393642CA58",
    "UploadJobs":[
        {
            "SourceURL":"http://****.mp4",
            "JobId":"ad90a501b1b94*****fb72374ad005046"
        }]
}

Error codes

For a list of error codes, visit the API Error Center.

Common errors

The following table describes the common errors that this operation can return.


Error code	Error message	HTTP status code	Description
InvalidParameter.UploadURLs	The specified parameter UploadURLs is not valid.	400	The error message returned because the UploadURLs parameter is invalid.

SDK examples

We recommend that you use a server SDK to call this operation. For more information about the sample code that is used to call this operation in various languages, see the following topics: