- URL:
- https://dataacccess/notebookworkspace/downloadFile
- Methods:
POST- Version Introduced:
- 11.5
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.
To access notebook-related endpoints, administrators must be assigned a custom role that includes any of the privileges listed above as well as the Create and edit notebooks privilege.
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 download operation allows a user to download a file from their notebook workspace directory (/arcgis/home). Only the owner of the file is allowed to download the file.
Request parameters
| Parameter | Details |
|---|---|
(Required) | The name of the file to be downloaded. Example |
| The response format. The default response format is Values: |
Example usage
The following is a sample POST request for the download operation:
POST /<context>/notebooks/admin/dataaccess/notebookworkspace/downloadFile HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-fprm-urlencoded
Content-Length: []
fileName=hydrology/mjwater.zip&f=pjson&token=PuuxoDV8HzHD1GxXUDpgHDeItErtl9Wr6rbULdhXHVUnGsjZ2hI1j1cPmnDEN1UnUfDqrNr2AuviTe5OkBumXsPlwSCrKw_ZVM1vczv2ziRESyz2PEAAhfsf71EyKIEGe7wW1z7hN_aLIjTekcdUbs-xtUAMZjEKHDRxT85NlfWqQghOy6o5XE54P8nnmdhllY6IfdtqeRtOYfFLoCBGCmOFV8diNVk4CxW3MMnzelDAGuRpN-Bru-vcYTY-7Or9JSON Response syntax
{
"status": "<success | failure>"
}JSON Response example
{
"status": "success"
}