UploadMediaByURL - ApsaraVideo VOD

Uploads media files based on URLs.

Operation description

You can call this operation to upload media files that are not stored on a local server or device and must be uploaded based on URLs over the Internet.
The URL-based upload jobs are asynchronous. After you submit a URL-based upload job by calling this operation, it may take hours, even days to complete. If you require high timeliness, we recommend that you use the upload SDK.
If you configure callbacks, you can receive an UploadByURLComplete event notification after the media file is uploaded. You can query the upload status by calling the GetURLUploadInfos operation.
After you submit an upload job, the job is asynchronously processed on the cloud. All URL-based upload jobs that are submitted in each region are queued. The waiting time for the upload job depends on the number of queued jobs. After the upload job is complete, you can associate the playback URL included in the callback with the media ID.
You can call this operation only in the China (Shanghai) and Singapore regions.
Every time you submit a URL-based upload job, a new media ID is generated in ApsaraVideo VOD.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
UploadURLs	string	Yes	The URL of the media file. You must include a file name extension in the URL, such as `https://****.mp4`. If the URL does not contain a file name extension, specify a file name extension for `FileExtension` in `UploadMetadatas`. If you specify `FileExtension` when the URL contains a file name extension, the file name extension that you specified for `FileExtension` takes effect. For more information about file name extensions supported by ApsaraVideo VOD, 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. You must encode URLs before you separate them with commas (,).	https://****.mp4
TemplateGroupId	string	No	The ID of the transcoding template group. You can use one of the following methods to obtain 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 > Transcoding Template Groups. On the Transcoding Template Groups page, view the ID of the transcoding template group. Obtain the value of TranscodeTemplateGroupId from the response to the AddTranscodeTemplateGroup operation. Obtain the value of TranscodeTemplateGroupId from the response to the ListTranscodeTemplateGroup operation. Note If you leave this parameter empty, the default transcoding template group is used for transcoding. If you specify this parameter, the specified transcoding template group is used for transcoding. You can also specify the ID of the transcoding template group in `UploadMetadatas`. If you specify this parameter and TemplateGroupId in UploadMetadatas, the TemplateGroupId in UploadMetadatas takes effect.	ca3a8f6e4957b65806709586****
StorageLocation	string	No	The storage address of the media file. To view the storage address, log on to the ApsaraVideo VOD console. In the left-side navigation pane, choose Configuration Management > Media Management > Storage. If you do not specify a storage address, the default storage address is used.	outin-bfefbb90a47c******163e1c7426.oss-cn-shanghai.aliyuncs.com
UploadMetadatas	string	No	The metadata of the media file that you want to upload. The value must be a JSON string. This parameter takes effect only if SourceURL matches the URL that you specified for UploadURLs. You must convert the JSON-formatted data such as `[UploadMetadata, UploadMetadata,…]` to a JSON string. For more information, see the UploadMetadata table.	[{"SourceURL":"https://example.aliyundoc.com/video01.mp4","Title":"urlUploadTest"}]
UserData	string	No	The custom configurations such as callback configurations and upload acceleration configurations. The value must be a JSON string. For more information, see Request parameters. Note The callback configurations take effect only after you specify the HTTP callback URL and select specific callback events in the ApsaraVideo VOD console. For more information about how to configure HTTP callback settings in the ApsaraVideo VOD console, see Configure callback settings. If you want to enable the upload acceleration feature, submit a request on Yida. For more information, see Overview .	{"MessageCallback":{"CallbackURL":"http://example.aliyundoc.com"},"Extend":{"localId":"xxx","test":"www"}}
AppId	string	No	The ID of the application. Default value: app-1000000. For more information, see Overview .	app-****
WorkflowId	string	No	The ID of the workflow. To view the ID of the workflow, log on to the ApsaraVideo VOD console. In the left-side navigation pane, choose Configuration Management > Media Processing > Workflows. Note If you specify WorkflowId and TemplateGroupId, the value of WorkflowId takes effect. For more information, see Workflows .	e1e243b42548248197d6f74f9****
SessionId	string	No	The custom identifier for deduplication. If you specify this parameter and send a request, an error is returned if a request with the same identifier was sent in the last 10 minutes. A custom identifier can be up to 50 characters in length and can contain letters, digits, hyphens (-), and underscores (_). If you do not specify this parameter or leave this parameter empty, duplicate requests are not filtered.	5c62d40299034bbaa4c195da330****

UploadMetadata

Parameter	Type	Required	Description
SourceURL	String	Yes	The URL of the media file that you want to upload.
Title	String	No	The title of the media file. The name 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. To view 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.
Tags	String	No	The tags of the media file. A tag can be up to 32 bytes in length. You can specify 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. If you specify this parameter, TemplateGroupId in the preceding table is overwritten.
WorkflowId	String	No	The ID of the workflow. If you specify WorkflowId and TemplateGroupId, WorkflowId takes precedence. For more information, see Workflows .
FileExtension	String	No	The file name extension of the media file. For more information about file name extensions supported by ApsaraVideo VOD, see Overview .

Note

You cannot include emoticons in parameters such as Title, Description, and Tags in UploadMetadata.

If you set TemplateGroupId to VOD_NO_TRANSCODE, the media file is uploaded without transcoding. In this case, only videos in the following formats can be played: MP4, FLV, MP3, M3U8, and WebM. Videos in other formats can be stored in ApsaraVideo VOD. You can identify the video format based on FileName. If you want to use ApsaraVideo Player, use ApsaraVideo Player V3.1.0 or later.

If you set TemplateGroupId to VOD_NO_TRANSCODE, only the FileUploadComplete event notification is returned when the media file is uploaded. The StreamTranscodeComplete event notification is not returned.

If you configure callbacks, you can receive an UploadByURLComplete event notification when the media file is uploaded. You can also receive the FileUploadComplete and StreamTranscodeComplete event notifications.

If you upload multiple media files in a batch, ApsaraVideo VOD sends an event notification for each media file when the media file is uploaded.

Response parameters

Parameter	Type	Description	Example
	object	The response parameters.
RequestId	string	The ID of the request.	25818875-5F78-4AF6-D7393642CA58****
UploadJobs	array<object>	The ID of the upload job.
	object	The details of the upload job.
SourceURL	string	The URL of the source file that is uploaded in the upload job.	http://example****.mp4
JobId	string	The ID of the upload job.	ad90a501b1b94fb72374ad005046****

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 success responses

JSONformat

{
  "RequestId": "25818875-5F78-4AF6-D7393642CA58****",
  "UploadJobs": [
    {
      "SourceURL": "http://example****.mp4",
      "JobId": "ad90a501b1b94fb72374ad005046****"
    }
  ]
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2023-05-16	The request parameters of the API has changed	View Change Details

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.