This Web API has an HTTP POST and a GET version.
- The GET request enables you to delete individual user Reputation entries, but it can also be used to delete all user-defined reputation entries, RepDV entries, or the ThreatDV URL package.
- The POST request enables you to use a CSV file to delete multiple user Reputation entries of the same type. This is convenient when you want to use the same CSV file that you used to import the user Reputation entries.
- You cannot set a query string to delete the user-defined Reputation entries. You must specify them individually in the GET request, and you must already have them in a CSV file to use the POST request.
- You can create a query for the records you want to delete, then save the response in a CSV file. After verifying the file contains the records you want deleted, you can use the file in a delete POST request.
- Each request can result in a distribution and a sync time to the managed devices. For optimal performance, when deleting multiple user defined reputation entries, delete the reputation entries with a file.
Definition
repEntries/delete
Using POST to delete multiple user Reputation entries with a CSV file
Follow these guidelines when using POST requests for deleting entries:
- The POST request can only delete user-defined entries.
- The CSV file can contain user Reputation entries in the same format that was used to import them.
- All user entries defined in the CSV file must be of the same type. Whatever type parameter you specify as a parameter is applied to the entire CSV file posted.
| Parameter | Type | Description |
| type | Any of the supported values | Import a file with Reputation entries to delete on the SMS. This enables you to delete
many reputation entries by using a file. Only one of the following types of entry
is permitted within a file:IPv4 or IPv6 address of the Reputation entry.
This parameter applies only to the POST request.
|
Examples
curl -v -X POST -k --header "X-SMS-API-KEY: <string>" -F "requestFile=@./repEntries-filehash-ipv4.csv" "https://<sms_server>/repEntries/delete?type=ipv4"
curl -v -X POST -k --header "X-SMS-API-KEY: <string>" -F "requestFile=@./repEntries-filehash-ipv6.csv" "https://<sms_server>/repEntries/delete?type=ipv6"
curl -v -X POST -k --header "X-SMS-API-KEY: <string>" -F "requestFile=@./repEntries-filehash-dns.csv" "https://<sms_server>/repEntries/delete?type=dns"
curl -v -X POST -k --header "X-SMS-API-KEY: <string>" -F "requestFile=@./repEntries-filehash-url.csv" "https://<sms_server>/repEntries/delete?type=url"
curl -v -X POST -k --header "X-SMS-API-KEY: <string>" -F "requestFile=@./repEntries-filehash-sha1.csv" "https://<sms_server>/repEntries/delete?type= filehash-sha1"
curl -v -X POST -k --header "X-SMS-API-KEY: <string>" -F "requestFile=@./repEntries-filehash-sha256.csv" "https://<sms_server>/repEntries/delete?type= filehash-sha256"
Using GET to delete Reputation entries (
Follow these guidelines when using GET requests for deleting entries:
- Use the GET request to delete not only user-defined entries but the ThreatDV URL package and all RepDV entries as well.
- You can use the GET request to delete individual user Reputation entries or user-defined entries across all types with a single request.
| Parameter | Type | Description |
| criteria | One of the supported values | Required. This parameter applies only to the GET request. The following values are
supported:
This parameter applies only to the POST request.
|
When the preceding criteria parameter is set specifically to entry, the following
parameters can also be provided.
| Parameter | Type | Description |
| ip | IP address | IPv4 or IPv6 address of the Reputation entry. |
| dns | string | Domain name of the Reputation entry. |
| url | URL | Reputation URL entry. |
| filehash | A prefixed file hash | An existing file hash entry with either a sha1: or sha256: prefix. |
Examples
curl -v -k --header "X-SMS-API-KEY: <string>" "https://<sms_server>/repEntries/delete?criteria=entry&ip=1.1.1.1&ip=1.1.1.2& dns=malware.source1.com&dns=malware.source2.com"
curl -v -k --header "X-SMS-API-KEY: <string>" "https://<sms_server>/repEntries/delete?criteria=entry&url=http://badurl.com/this/is/nice"
curl -v -k --header "X-SMS-API-KEY: <string>" "https://<sms_server>/repEntries/delete?criteria=entry&filehash=sha1:b7c74f7fbde596ba87ac98ff4 a9c8235d437ebce"
curl -v -k --header "X-SMS-API-KEY: <string>" "https://<sms_server>/repEntries/delete?criteria=entry&filehash=sha256:1c17d07a2762f6baab41004b57 eec113774bc3f745d4c1d64c0fe464720a2126"
