- URL:
- https://<root>/services/types/customrasterfunctions/<customRasterFunctionID>/delete
- Methods:
POST- Version Introduced:
- 12.2
Access requirements
Required privileges
The Server 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.
Note that administrators assigned a custom role must also have the administrative View all content privilege assigned to them to access the API directory as an administrator.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the ArcGIS Server 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 ArcGIS Server Administrator API generate operation. For security reasons, all POST requests made to the ArcGIS Server Administrator API must include a token in the request body.
Description
The delete operation deletes a registered custom raster function and its corresponding raster function portal item from a server. If a custom raster function has been updated since it was initially registered, developers should delete the outdated custom raster function and re-register the updated raster function template. The HTML view will return to the Custom Raster Functions resource.
Request parameters
| Parameter | Details |
|---|---|
(Optional) | The response format. The default format is Values: |
Example usage
The following is a sample POST request for the register operation:
POST /<context>/admin/services/types/customrasterfunctions/ba60574dbf4947859188186f3b69a276/delete HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []
f=pjson&token=<ACCESS_TOKEN>JSON Response example
{
"status": "success"
}