- URL:
- https://<root>/notebooks/workspaces/<workspaceId>
- Methods:
GET- Version Introduced:
- 11.4
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
A workspace resource returns information about the notebook workspace that is registered with your organization. The properties of a workspace includes properties defined during the workspace creation, as well as auto-generated information provided after the workspace was created (the mount and id properties). This resource also provides access to the Status resource for checking the status of the workspace and the Delete operation that administrators can use to delete the notebook workspace.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default response format is Values: |
Example usage
The following is a sample request URL used to access a workspace resource:
https://organization.example.com/<context>/admin/notebooks/workspaces/utz5kgaz4vd6dpj3xrsyb?f=jsonJSON Response example
{
"name": "arcgis-notebooks-workspace",
"id": "utz5kgaz4vd6dpj3xrsyb",
"type": "PVC",
"spec": {
"storageClassName": "arcgis-storage-default",
"volumeName": "",
"resources": {
"requests": {"storage": "100Gi"},
"limits": {}
},
"accessModes": ["ReadWriteMany"],
"volumeMode": "Filesystem"
},
"managedKubernetesResources": [{
"purpose": "pvc",
"kind": "PersistentVolumeClaim",
"name": "arcgis-nb-workspace-volume-utz5kgaz4vd6dpj3xrsyb"
}],
"revision": 1,
"info": {
"volumeIdentifier": "",
"volumePath": "/arcgis/home"
}
}JSON Response example 2
{
"name": "arcgis-notebooks-workspace",
"id": "uokbqwtd8ciyeb07oyal2",
"type": "PVC",
"spec": {
"storageClassName": "",
"volumeName": "notebooksworkspace-pv-ar-123456789",
"resources": {
"requests": {"storage": "135Gi"},
"limits": {}
},
"accessModes": ["ReadWriteMany"],
"volumeMode": "Filesystem"
},
"managedKubernetesResources": [{
"purpose": "pvc",
"kind": "PersistentVolumeClaim",
"name": "arcgis-nb-workspace-volume-uokbqwtd8ciyeb07oyal2"
}],
"revision": 1,
"info": {
"volumeIdentifier": "",
"volumePath": "/arcgis/home"
}
}