Remove a rule from a groupBeta
Enabled per organisation
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.Removes the rule from the definition and queues its removal from every address the group reaches.
Authorization
orgApiKey firewall-groups.manageAn 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-groups.manage
Path Parameters
The group's id, as returned by the list endpoint. A group belonging to
another organisation is a 404, never a 403 — a 403 would confirm
the id is real.
The rule's id, as returned when reading the group.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/firewall/groups/42/rules/7"{ "data": { "operation_id": 0 }, "message": "string"}Replace a rule in a group PATCH
The body is the rule's whole new definition, not a partial patch — fields belonging to other kinds are cleared, so a…
Report what applying this group would do POST
Writes nothing. It takes a body because it takes a list of addresses, not because it changes anything — which is why…