Re-queue one address that failed

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.

Clears the recorded error and re-queues that address, forced past the usual "already at this revision" check — the point of a retry is that the recorded state is not trusted.

Read last_error on the assignment first. A rejection from the mitigation network names the rule it refused, and retrying blind will queue the same failure again.

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

Path Parameters

group*integer

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.

ip*string

An address this group is currently applied to.

Formatipv4

Response Body

`application/json`

curl -X POST "https://example.com/firewall/groups/42/assignments/192.0.2.10/retry"

{  "data": {    "operation_id": 0,    "assignment": {      "ip": "192.168.0.1",      "prefix": "string",      "status": "pending",      "applied_revision": 0,      "last_error": "string",      "last_synced_at": "2019-08-24T14:15:22Z"    }  },  "message": "string"}

Re-queue one address that failedBeta

Authorization

Path Parameters

Response Body

200application/json

401application/json

403application/json

404application/json

429application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`