- URL:
- https://<root>/uploads/register
- Methods:
POST- 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 generate 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.
Description
The register operation directs the server to reserve space for a new item (to be uploaded) that could be made up of one or more parts. Once the operation is completed, you must use the upload part operation to upload individual parts. After you have uploaded all the parts, you must ask the server to consolidate the upload by committing it.
Request parameters
| Parameter | Details |
|---|---|
| A name for the item. Example |
| An optional description for item to be uploaded. Example |
| The response format. The default response format is Values: |
Example usage
The following is a sample POST request for the register operation:
POST /<context>/admin/uploads/register HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []
itemName=TestUpload_WaterDistributionNetwork.kmz&description=Test upload of Water Distribution Network template&f=pjsonJSON Response syntax
{
"status": "success",
"item": <item>
}JSON Response example
{
"status": "success",
"item": {
"itemID": "ie3b7610b-b229-4ca0-a8bc-d2c02069149a",
"itemName": "TestUpload_WaterDistributionNetwork.kmz",
"description": "Test upload of Water Distribution Network template",
"pathOnServer": "C:\\arcgis\\arcgisserver\\directories\\arcgissystem\\kml",
"date": 1566936940842,
"committed": false,
"serviceName": "",
"contentType": "application/octet-stream"
}
}