AddStoryFiles - Intelligent Media Management - Alibaba Cloud Documentation Center

Adds objects to a story.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
imm:AddStoryFiles	none	*Dataset `acs:imm:{#regionId}:{#accountId}:project/{#ProjectName}/dataset/{#DatasetName}`	none	none

Request parameters

Parameter	Type	Required	Description	Example
ProjectName	string	Yes	The name of the project.	test-project
DatasetName	string	Yes	The name of the dataset.	test-dataset
ObjectId	string	Yes	The ID of the story.	testid
Files	array<object>	Yes	The objects that you want to add.
	object	Yes	The information about the object.
URI	string	No	The URI of the object. Specify the OSS URI in the oss://${Bucket}/${Object} format, where `${Bucket}` is the name of the bucket in the same region as the current project and `${Object}` is the path of the object with the extension included.	oss://test-bucket/test-object

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	6E93D6C9-5AC0-49F9-914D-E02678D3****
Files	array<object>	The objects that were added.
Files	object	The information about the object.
URI	string	The URI of the object. The OSS URI follows the `oss://{bucketname}/{objectname}` format, where `bucketname` is the name of the bucket in the same region as the current project and `objectname` is the path of the object with the extension included.	oss://test-bucket/test-object
ErrorCode	string	The error code.	ResourceNotFound
ErrorMessage	string	The error message that is returned.	The specified resource %s is not found.

Examples

Sample success responses

JSONformat

{
  "RequestId": "6E93D6C9-5AC0-49F9-914D-E02678D3****",
  "Files": [
    {
      "URI": "oss://test-bucket/test-object",
      "ErrorCode": "ResourceNotFound",
      "ErrorMessage": "The specified resource %s is not found."
    }
  ]
}

Error codes

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

Change history

Change time	Summary of changes	Operation

No change history