server/api/api.html [62:90]: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Remove a whitelist entry

JSON parameters:

force: (boolean) Force addition, even if it means removing conflicting rules already in the DB
reason: (string) The reason for banning
rule: (string) the ID of an existing rule
source: (string) the source IP Address or Network
target: (string) Target machine to ban on (or * for all machines)
timeout: (integer) If present and greater than 0, denotes the UNIX timestamp when this rule stops working

Input examples:

application/json:
{}

Response examples:

200:
{
    "message": "Action completed"
}
default:
{
    "code": 403,
    "reason": "You need to be logged in to view this endpoint!"
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - server/api/api.html [391:419]: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Remove a whitelist entry

JSON parameters:

force: (boolean) Force addition, even if it means removing conflicting rules already in the DB
reason: (string) The reason for banning
rule: (string) the ID of an existing rule
source: (string) the source IP Address or Network
target: (string) Target machine to ban on (or * for all machines)
timeout: (integer) If present and greater than 0, denotes the UNIX timestamp when this rule stops working

Input examples:

application/json:
{}

Response examples:

200:
{
    "message": "Action completed"
}
default:
{
    "code": 403,
    "reason": "You need to be logged in to view this endpoint!"
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -