- URL:
- https://<root>/notebooks/snapshots/restore
- Methods:
POST- 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
The restore operation allows you to restore a notebook snapshot for a notebook item. Only the owner of a notebook is allowed to restore from a snapshot.
Request parameters
| Parameter | Details |
|---|---|
(Required) | The item ID of the notebook to list snapshots from. |
(Required) | The resource key of the snapshot to restore. Example: |
| A title for the snapshot preserved as part of the restore. |
| The option of whether to preserve the current notebook item file as a snapshot as part of the restore. Values: |
| A description for the snapshot preserved as part of the restore. Values: |
| The response format. The default response format is Values: |
Example usage
The following is a sample POST request for the restore operation:
POST /<context>/admin/notebooks/snapshots/restore HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []
itemId=2ff206ba534541428409e327d03588d1&resourceKey=snapshot-0f146a4ba1964327b396b9be5f1042ed.json&title=&preserveCurrentAsSnapshot=false&description=false&f=pjson&token=<token>JSON Response example
{
"status": "success"
}