- URL:https://[root]/content/users/[userName]/items/[itemID]/updateResources(POST only)
- Version Introduced:
Example usage
URL for Update Resources
https://www.arcgis.com/sharing/rest/content/users/jsmith/items/0c66beb52dff4994be67937cdadbdb1f/updateResourcesDescription
The updateResources operation allows you to update an item's existing file resources . 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 (except 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. The operation is only available to the item owner, organization administrator and members of the group with item update capability.
This operation supports the following file formats:
- .json
- .xml
- .txt
- .png
- .pbf
- .zip
- .jpeg
- .jpg
- .gif
- .bmp
- .gz
- .svg
- .svgz
- .geodatabase
File resources must be uploaded in an https multipart request pursuant to IETF RFC1867.
Request parameters
| Parameter | Details |
|---|---|
| [Common Parameters] | For a complete listing, see Common parameters. |
| file (Optional) | Multipart https parameter containing the binary file to upload. |
| resourcesPrefix (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. The updated file resources can be accessed either by: |
| fileName (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. |
| text (Optional) | Text input to update an existing text resource, used together with fileName. |
| access (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 |
| f | The response format. The default format is html. Values: html | json | pjson |
Response properties
| Property | Details |
|---|---|
| success | Indicates whether the operation was successful. |
| itemId | The ID of the item that file resources were added to. |
| owner | The owner of the item. |
| folder | The ID of the folder where the item is; null if the item is in the root folder. |
JSON Response syntax
{
"success": true,
"itemId": "<item id>",
"owner": "<owner username>",
"folder": "<folder id>"
}JSON Response example
Note:
Two possible errors that can occur for this operation are error code 404 (resource does not exist or is inaccessible) and error code 400 (exceeded total number of files for this resource).
{
"success": true,
"itemId": "0c66beb52dff4994be67937cdadbdb1f",
"owner": "jsmith",
"folder": null
}