List supported protection applications
GET
The catalogue a rule is built from — one entry per protocol-aware filter the network offers. Identical for every account, and the source of the applicationId a rule needs.
apiToken firewall:readheader
AuthorizationBearer <token>A personal API token: Authorization: Bearer dh_live_…. See Authentication for scopes.
Scope: firewall:read
The presets.
application/json- response
items*array<>curl -X GET 'https://api.deluxhost.net/v1/firewall/applications' \ -H "Authorization: Bearer $DELUXHOST_TOKEN"Example Response
{ "items": [ { "id": 0, "name": "string", "protocol": "string", "note": "string" } ]}Delete a protection rule DELETE
`ip` is required. Rule ids are a global sequence upstream, so the rule is checked to exist **for that address** before anything is deleted; anything else is a `404`. Removing a rule does not take the address offline — it falls back to the network's default filtering. Recreating it is one `POST` away, which is why this is the one thing a token is allowed to delete.
Mark a notification as read POST