- URL:
- https://<root>/uploads/<itemID>
- Methods:
GET- Operations:
- Commit, Upload Part, Download, Delete
- Version Introduced:
- 10.9
Access requirements
Required privileges
The Enterprise Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Enterprise Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Enterprise Directory API. For security reasons, all POST requests made to the Enterprise Administrator API must include a token in the request body.
Description
The resource for an item uploaded to the server. Various workflows upload items and then process them on the server. For example, when publishing a GIS service from ArcGIS Pro, the application first uploads the service definition (.) to the server and then invokes the publishing geoprocessing tool to publish the service.
The resource for the uploaded item returns the following information for the uploaded item:
- Item ID (
item)—A unique identifier that is specific to each uploaded item.ID - Description (
description)—If a description was added to the uploaded item as part of the upload request, it will be reflected in this property. - Item Name (
item)—The file name of the uploaded item.Name - Date (
date)—The date the item was uploaded, represented in milliseconds from epoch. - Committed (
committed)—This property returns as true when the upload of individual parts is completed. - Content Type (
content)—The content type of the uploaded file, for example,Type application/octet-stream.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default response is Values: |
Example usage
The following is a sample request URL used to access an individual uploaded item resource:
https://organization.example.com/<context>/admin/uploads/3aecbde2-d8aa-46d5-9653-26e9695062a4?f=pjsonJSON Response syntax
{
"itemID": "<ID>",
"description": "<description>",
"itemName": "<name>",
"date": "<date of upload>",
"committed": <true|false>,
"contentType": "<file content type>"
}JSON Response example
{
"itemID": "3aecbde2-d8aa-46d5-9653-26e9695062a4",
"description": "",
"itemName": "FireWeatherWatch.kmz",
"date": 1597190283335,
"committed": true,
"contentType": "application/octet-stream"
}