Skip to content
URL:
https://<root>/uploads/<uploadID>
Methods:
GET
Operations:
Commit Item, Delete Item, Upload Part, Item Parts
Version Introduced:
10.1

Access requirements

Required privileges

The Sever 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.



Note that administrators assigned a custom role must also have the administrative View all content privilege assigned to them to access the API directory as an administrator. Additonally, any custom roles that include a webhook-related privilege must also include the general Publish server-based layers content privilege.

Tokens

This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Server 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 generateToken operation in the Portal Directory API. For security reasons, all POST requests made to the Server Administrator API must include a token in the request body.


Learn how to generate a token

Description

The individual item resource represents an item that has been 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 or ArcGIS Server Manager, the application first uploads the service definition (.sd) to the server and then invokes the publishing geoprocessing tool to publish the service.

Each uploaded item is identified by a unique name (itemID). The pathOnServer property locates the specific item in the ArcGIS Server system directory. The committed parameter is set to true once the upload of individual parts is complete.

Request parameters

ParameterDetails

f

The response format. The default response format is html.

Values: html | json | pjson

Example usage

The following is a sample request URL used to access an individual uploaded item resource:

Use dark colors for code blocksCopy
1
https://organization.example.com/<context>/admin/uploads/if4582d33-f10a-41fe-85bc-cf2e2880c46e?f=pjson

JSON Response syntax

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
{
  "itemID": "<ID>",
  "itemName": "<name>",
  "description": "<description>",
  "pathOnServer": "<path_on_server>",
  "date": "<date_of_upload>",
  "committed": <true|false>
}

JSON Response example

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
{
  "itemID": "if4582d33-f10a-41fe-85bc-cf2e2880c46e",
  "itemName": "JavaDeleteFeatures.sd",
  "description": null,
  "pathOnServer": "c:\\arcgisserver\\directories\\arcgissystem\\arcgisuploads\\if4582d33-f10a-41fe-85bc-cf2e2880c46e",
  "date": "Mon Jun 13 12:59:59 PDT 2011",
  "committed": true
}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.