- URL:
- https://<root>/uploads/<uploadID>/uploadPart
- Methods:
POST- 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 upload operation uploads one part of an item. Before uploading parts, use the Register operation to reserve space for the item on the server. Once all the necessary parts have been uploaded to create the item using upload, use the Commit operation to consolidate the parts.
Request parameters
| Parameter | Details |
|---|---|
(Required) | An integer value associated with the part. |
(Required) | The file for the part being uploaded, processed as a multipart POST file. |
| The response format. Currently, the only supported format is |
Example usage
The following is a sample POST request for the upload operation:
POST /<context>/admin/uploads/e753e856-85d1-4d14-a637-98ffabcefa7f/uploadPart HTTP/1.1
Host: organization.example.com
Content-Type: multipart/form-data; boundary=------boundary
------boundary
Content-Disposition: form-data; name="partFile"; filename=""
Content-Type: application/octet-stream
partExample.zip
------boundary
Content-Disposition: form-data; name="partNumber"
1
------boundary
Content-Disposition: form-data; name="f"
html
------boundary
Content-Disposition: form-data; name="token"
vwEAbH7_sOBZUAtBtjpYs03RrGPgyJZmbmJ-PbnWyqfiC5y0udRik8fpi4sqSWoPV05519X9dZsUa9iG4PdGcBKAUGBR1lnQ-oGKxuwkruJj_hokpTl2lmPCbaAO6xW1ESvj66u9fDKij4OOLr5KZ-sA88hJ8dd-NiBhUPDlxpAgo_7TuVftRZadgf4kPkQBTplkE4KsRJ-FGv6ZtIO7FL8Pw745LrFqTT7DcTfgpKk3EecY-pzMhHU9z3ULZ54d
------boundary--