hosting
GET /v1/sites/{siteId}/cdn/firewall-rules
List a site's custom edge firewall rules.
Authentication
Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/cdn/firewall-rules \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
The zone's custom block/challenge rules, **in evaluation order**. Rules written in the customer's own provider dashboard are included and flagged `foreign: true`; they are editable here, because it is their account. `expression` is the provider's own matching syntax, passed through unchanged. A neutral matching language that every adapter half-implemented would be a rule that silently matches nothing. Requires `sites.view`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
supported | boolean | Yes | — |
rules | CdnFirewallRule[] | Yes | In evaluation order. The provider's custom-rules phase is terminating — the first match decides. |
Errors this endpoint can return
401 · 403 · 404 · 429 · 503