---
title: "Create a request for a wider range"
url: https://docs.corefinity.com/api/reference/firewall/create-firewall-range-request
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_range_request.md
---
# Create a request for a wider range

Asks Corefinity to allow a range wider than /24: IPv4 /9 to /23, or IPv6 /9 to /47. The entry is made at once with the status `pending_approval` and allows nothing until Corefinity approves it; it then reads `active`, or `rejected` with the reason.

```http
POST /api/firewall/range-requests
```

- Scope: `write`
- Two-factor: required on your account (all)
- Rate limit: 10 an hour; 30 a minute for each person; 120 a minute for each company
- Try it in the console: off. It has not been cleared for the console. Copy the request and run it yourself when you are sure.

## Body

- `address` (string, required): A range in CIDR form, IPv4 /9 to /23 or IPv6 /9 to /47.
- `expires_in_days` (integer or null): After how many days the address stops being allowed. Null, or left out, for no expiry. One of `1`, `30`, `90`, `365`, `null`.
- `owner_id` (integer, required)
- `owner_type` (string, required): The level an address is held at. `user` is yourself. One of `environment`, `website`, `company`, `user`.
- `reason` (string, required): Why you need the range. Corefinity reads it when deciding.
- `scope` (string): Left out, the range gets `both`. What the address may reach. `ssh` is SSH only, `web` the website only, `both` both. One of `both`, `ssh`, `web`.

## Request

### curl

```bash
curl -X POST https://manage.corefinity.com/api/firewall/range-requests \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "address": "2001:db8:4a00::/40",
    "owner_id": 1204,
    "owner_type": "company",
    "reason": "Our office network. Every workstation gets an address from this range."
  }'
```

### PHP

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

$response = Http::withToken(env('COREFINITY_TOKEN'))
    ->acceptJson()
    ->post('https://manage.corefinity.com/api/firewall/range-requests', [
        'address' => '2001:db8:4a00::/40',
        'owner_id' => 1204,
        'owner_type' => 'company',
        'reason' => 'Our office network. Every workstation gets an address from this range.',
    ]);

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

### Node

```javascript
const res = await fetch('https://manage.corefinity.com/api/firewall/range-requests', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
    Accept: 'application/json',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    address: '2001:db8:4a00::/40',
    owner_id: 1204,
    owner_type: 'company',
    reason: 'Our office network. Every workstation gets an address from this range.',
  }),
});

// 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.post(
    "https://manage.corefinity.com/api/firewall/range-requests",
    headers={
        "Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
        "Accept": "application/json",
    },
    json={
        "address": "2001:db8:4a00::/40",
        "owner_id": 1204,
        "owner_type": "company",
        "reason": "Our office network. Every workstation gets an address from this range.",
    },
)

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

## Responses

### 202 The request was filed. `entry.status` is `pending_approval`.

```json
{
  "entry": {
    "added_by": {
      "name": "Eleanor Finch",
      "on_behalf_of": null,
      "support": false
    },
    "carried_from": null,
    "changed_at": "2026-11-06T09:16:40Z",
    "cidr": "2001:db8:4a00::/40",
    "comment": null,
    "created_at": "2026-11-06T09:16:40Z",
    "decision_reason": null,
    "editable": true,
    "expires_at": null,
    "family": 6,
    "id": 9006,
    "layer": "company",
    "owner": {
      "id": 1204,
      "name": "Harbour & Finch",
      "type": "company"
    },
    "path": null,
    "request_reason": "Our office network. Every workstation gets an address from this range.",
    "scope": {
      "ssh": true,
      "web": true
    },
    "source": "manual",
    "status": "pending_approval",
    "web_paused": false
  }
}
```

### 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` (a field is missing, wrong or not part of the request, or `address` is an address or a range of /24 (IPv6 /48) or narrower, which needs no approval; `field` names it), `firewall_address_invalid`, `firewall_width_refused` (a range of /8 or wider), `firewall_address_refused` (a private, reserved or provider range), `firewall_duplicate`, `firewall_scope_invalid` or `firewall_cap_exceeded` (the list holds its limit of addresses; a request waiting for approval counts).

```json
{
  "code": "firewall_cap_exceeded",
  "field": null,
  "message": "This list already holds its limit of 200 addresses.",
  "reason": "firewall_cap_exceeded"
}
```

### 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 | `firewall_cap_exceeded` | This list already holds its limit of 200 addresses. |
| 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_range_request`](https://docs.corefinity.com/mcp/tools/corestack_firewall_range_request.md)
