- URL:https://[root]/content/users/[userName]/items/[itemID]/updateResources(POST only)
- Version Introduced:
URL for Update Resources
The update resources operation (POST only) allows you to update existing file resources of an item. File resources use storage space from your quota and are scanned for viruses. The item size is updated to include the size of updated resource files. There is a limit of 1,000 files per item (expect Style items). A maximum of 50 files can be added for each request. Each file should be no more than 50 Mb. The maximum size of all of the file resources for an item is 10 GB.
Supported file formats are: .json, .xml, .txt, .png, .pbf, .zip, .jpeg, .jpg, .gif, .bmp, .gz, .svg, .svgz, and .geodatabase.
File resources must be uploaded in an https multipart request pursuant to IETF RFC1867.
The operation is only available to the item owner and the organization administrator.
For a complete listing, see Common parameters.
(Optional) Multipart https parameter containing the binary file to upload.
(Optional) Folder name used as a prefix of existing file resources to be updated. Resources prefix has to match that of the existing file resources to update successfully.
(Optional) File name used to rename one uploaded file or used together with text input to match existing item resource name.
For example, you can use fileName=banner.png to update an existing resource banner.png with a file named billboard.png without renaming the file locally.
(Optional) Text input to update an existing text resource, used together with fileName.
(Optional) Set file resource to be private regardless of the item access level, or revert it by setting it to inherit, which makes the item resource have the same access as the item. It can be passed in with fileName and optionally resourcesPrefix to update an existing item resource's access level.
Supported values: private | inherit
Indicates whether the operation was successful.
The ID of the item that file resources were added to.
The owner of the item.
The ID of the folder where the item is; null if the item is in the root folder.
JSON Response syntax
"itemId": "<item id>",
"owner": "<owner username>",
"folder": "<folder id>"
JSON Response example
"message": "Resource does not exist or is inaccessible.",
"message": "Exceeded total number of files for this resource",
"details" : [ ]