GET /v1/sites/{siteId}/cdn/page-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/page-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

Legacy URL-pattern page rules, in priority order. There is deliberately **no create** endpoint: page rules are a retiring provider product and the modern answer to almost everything they did is a cache rule or a redirect rule. A customer must be able to see and retire what they already have, and must not be led into building more of it. Requires `sites.view`.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 429 · 503