API ReferenceFirewall

Delete firewall rules by id

Enabled per organisation

This endpoint answers 403 until our staff enable the Firewall API flag on your organisation, and its ability cannot be granted to a key before then. Open a ticket saying what you intend to build — see Activation.
DELETE
/firewall/ips/{ip}/rules

Ids not present on this address are skipped silently rather than reported, so deleted may be lower than the number of ids you sent. A rule a firewall group owns cannot be deleted here — edit the group.

Authorization

orgApiKey firewall.manage
AuthorizationBearer <token>

An organisation API key, prefixed tbk_. Create one under Organisation to API keys; the plaintext is shown once.

The scopes listed on each operation are the abilities the key must carry. They are not OAuth scopes and are not negotiated per request.

In: header

Scope: firewall.manage

Path Parameters

ip*string

An address inside a prefix you announce, or one assigned to one of your services. Anything else is a 404.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/firewall/ips/192.0.2.10/rules" \  -H "Content-Type: application/json" \  -d '{    "ids": [      1    ]  }'
{  "data": {    "deleted": 0,    "ids": [      0    ]  },  "message": "string"}

Remove stateful filters DELETE

Takes the type:port keys the read endpoint publishes. Use those rather than assembling the key yourself — the format…

List the filter types available for one IP GET

Published per address because the catalogue is narrower under a service than under a prefix. A caller that guessed…