- URL:
- https://<root>/notebooks/webhookReceivers/<webhook receiver id>/delete
- 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 delete operation allows administrators to remove a registered service webhook receiver from ArcGIS Notebook services. It is important to note that any associated webhooks, such as those linked to asynchronous geoprocessing services, feature services, or organization webhooks, must be updated to eliminate references to this specific webhook receiver.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default is Values: |
Example usage
The following is a sample POST request for the delete operation:
POST /<context>/admin/notebooks/webhookReceivers/<webhook_receiver_id>/delete
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: [ ]
f=pjsonJSON Response syntax
{"status": "success|failure"}JSON Response example
{"status": "success"}