Remove allowed IPs

DELETE

/ipaware/{hostname}/allowed_ips

Last modified:2026-10-09 00:59:40

OperationId:removeAllowedIp

Removes addresses or CIDR ranges from the allow list on one server. The other servers in the cluster receive the change shortly after. Requires Super User scope.

Send the address in the body, or in the cidr query parameter. It must match the entry as stored. Send an array, or repeat the query parameter, to remove several in one call. Only entries added to this server's own list can be removed; builtin, url, and vendor entries cannot.

If your client cannot send a body with DELETE, use POST /ipaware/{hostname}/allowed_ips/remove.

The request goes to the IP rules service on {hostname}, and its status and body come back unchanged. Errors the API decides itself use the code and message form; errors from the service use the error form.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Query Params

Body Params application/json

Examples

Responses

🟢200OK

application/json

Every item was processed. An entry that did not exist answers not_found, not an error.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠429Too Many Requests

🔴503Service Unavailable

🟠404Not Found

🟢207Multi-Status

Request Example

Shell

JavaScript

Java

Swift

cURL

One subnetBatch

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/ipaware//allowed_ips?cidr=198.51.100.0%2F24' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "cidr": "198.51.100.0/24"
}'

Response Example

200 - One subnet

{
    "status": "removed",
    "cidr": "198.51.100.0/24",
    "store": "db",
    "removed": true
}

Modified at 2026-10-09 00:59:40

Add allowed IPs

Remove allowed IPs with POST