---
title: "Delete a firewall entry"
url: https://docs.corefinity.com/api/reference/firewall/delete-firewall-entry
type: endpoint
last_updated: 2026-11-13
feature: firewall
related:
  - https://docs.corefinity.com/guides/sites/access-and-security/firewall.md
  - https://docs.corefinity.com/mcp/tools/corestack_firewall_entry_remove.md
---
# Delete a firewall entry

Removes an address from its list. Send the address back in `confirm_address`, in the request body, exactly as
the list shows it in `cidr`. The entry reads `removing` until the address is gone from every environment it
reached.

```http
DELETE /api/firewall/entries/{entry}
```

- Scope: `write`
- Two-factor: required on your account (all)
- Rate limit: 120 a minute; 30 a minute for each person; 120 a minute for each company
- Long-running: answers with an operation to poll
- Try it in the console: off. It deletes data that cannot be brought back. Copy the request and run it yourself when you are sure.

## Path parameters

- `entry` (integer, required): The id of a firewall entry, as the lists answer it in `id`. Digits only.

## Body

- `confirm_address` (string, required): The entry's address, exactly as the lists answer it in `cidr`.

## Request

### curl

```bash
curl -X DELETE https://manage.corefinity.com/api/firewall/entries/9001 \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "confirm_address": "203.0.113.7/32"
  }'
```

### PHP

```php
use Illuminate\Support\Facades\Http;

$response = Http::withToken(env('COREFINITY_TOKEN'))
    ->acceptJson()
    ->delete('https://manage.corefinity.com/api/firewall/entries/9001', [
        'confirm_address' => '203.0.113.7/32',
    ]);

$data = $response->json();
```

### Node

```javascript
const res = await fetch('https://manage.corefinity.com/api/firewall/entries/9001', {
  method: 'DELETE',
  headers: {
    Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
    Accept: 'application/json',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    confirm_address: '203.0.113.7/32',
  }),
});

// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);
```

### Python

```python
import os
import requests

res = requests.delete(
    "https://manage.corefinity.com/api/firewall/entries/9001",
    headers={
        "Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
        "Accept": "application/json",
    },
    json={
        "confirm_address": "203.0.113.7/32",
    },
)

data = res.json() if res.content else None
```

## Responses

### 202 The removal was started. Follow `change_id` with `GET /firewall/changes/{change}`. An entry that is already being removed answers the change of the removal under way.

```json
{
  "change_id": 5313
}
```

### 401 No token, or a token that is not valid.

```json
{
  "message": "Unauthenticated."
}
```

### 403 The token lacks the `write` scope (`scope_required`), your company requires two-factor authentication and you have not set it up (`two_factor_required`), or you can see the entry or preset but may not change it, as with one your agency holds (`firewall_not_editable`).

```json
{
  "code": "company_unavailable",
  "message": "Your company is unavailable.",
  "reason": "company_unavailable"
}
```

### 404 The id does not exist or is something you cannot reach (`not_found`; both answer the same body), or the firewall is not on for it (`feature_off`).

```json
{
  "code": "feature_off",
  "message": "Not found.",
  "reason": "feature_off"
}
```

### 422 The request was refused. `reason` says why: `invalid_arguments` (`confirm_address` is missing, or a field is not part of the request; `field` names it) or `confirm_mismatch` (`confirm_address` is not the entry's address).

```json
{
  "code": "confirm_mismatch",
  "errors": {
    "confirm_address": [
      "The confirmation does not match."
    ]
  },
  "field": "confirm_address",
  "message": "The confirmation does not match.",
  "reason": "confirm_mismatch"
}
```

### 429 Too many requests: the endpoint's request limit (`rate_limited`, with `Retry-After`), or the firewall's own budget of 30 changes a minute for you and 120 for your company, which the Control Panel and AI assistants spend too (`firewall_throttled`). The budget's answer names no wait: try again after a minute.

```json
{
  "code": "firewall_throttled",
  "field": null,
  "message": "Too many firewall changes. Wait a minute and try again.",
  "reason": "firewall_throttled"
}
```

## If it is refused

| Status | Reason | What to do |
|---|---|---|
| 401 |  | Send a valid token as `Authorization: Bearer <token>`. |
| 403 | `company_unavailable` | Your company is unavailable. |
| 403 | `firewall_not_editable` | You can see this entry but you cannot change it. |
| 403 | `scope_required` | Use a token with the scope named in `scope`. |
| 403 | `two_factor_required` | Turn on two-factor on your account, then send again. |
| 404 | `feature_off` | This feature is not on for your organisation yet. |
| 404 | `not_found` | Not found. |
| 422 | `confirm_mismatch` | Send the confirmation exactly as the field named in `field` asks for it. |
| 422 | `invalid_arguments` | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
| 429 | `firewall_throttled` | Too many firewall changes. Wait a minute and try again. |
| 429 | `rate_limited` | Wait for the seconds in `Retry-After`. |

## The same task elsewhere

- Guide: [Firewall](https://docs.corefinity.com/guides/sites/access-and-security/firewall.md)
- MCP tool: [`corestack_firewall_entry_remove`](https://docs.corefinity.com/mcp/tools/corestack_firewall_entry_remove.md)
