GET /v1/sites/{siteId}/firewall/blocked

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}/firewall/blocked \
  -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

Refused requests (403/429) for the site's own hostnames, newest first, from the server's access log — at most 100, over the last hours (1-72, default 24). reason is a hint at the layer that answered (secret_files, core_files, attack_tools, login, xmlrpc, admin_trusted_only, a rule-set key, or rule), never a verdict. available is false when the log store could not be read — never an empty list that would read as "nothing was blocked". Requires sites.view.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 429