API ReferenceGroupsBeta

Create a firewall groupBeta

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.
POST
/firewall/groups

Creates an empty group. It reaches no addresses and changes nothing until you add rules and assign it.

Authorization

orgApiKey firewall-groups.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-groups.manage

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

curl -X POST "https://example.com/firewall/groups" \  -H "Content-Type: application/json" \  -d '{    "name": "string"  }'
{  "data": {    "id": 0,    "name": "string",    "description": "string",    "revision": 0,    "rule_count": 0,    "footprint": {      "ip": 0,      "geo": 0,      "filter": 0    },    "assignment_count": 0,    "updated_at": "2019-08-24T14:15:22Z"  },  "message": "string"}

List your firewall groups GET

Summaries only. footprint is what the group expands to on each address — one rule spanning ten ports is ten objects…

Read one group, its rules and the addresses it reaches GET

assignments lists only live addresses; one the group has been detached from is history and is not returned.