hosting

GET /v1/sites/{siteId}/cache

Get a site's server-side cache policy.

Alle hosting Endpunkte

Authentifizierung

Senden Sie einen API-Schlüssel als Bearer-Token. Der Schlüssel muss über die Berechtigung sites.view verfügen; ein Schlüssel ohne diese wird mit 403 statt 404 abgelehnt.

Dieser Endpunkt erfordert keine Organisations-ID. Ihr Schlüssel identifiziert bereits die zugehörige Organisation, und die Antwort ist entsprechend eingeschränkt.

Ausprobieren

Ersetzen Sie alles in spitzen Klammern durch Ihre eigenen Werte und den Platzhalter für den Schlüssel durch einen Schlüssel aus Ihrem Dashboard.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/cache \
  -H "Authorization: Bearer zdk_live_…"

Angemeldet? Die API-Konsole in Ihrem Dashboard trägt automatisch Ihre echte Organisations-ID sowie Ihren eigenen Schlüssel ein und führt die Anfrage gegen die Live-API aus, sodass Sie die tatsächliche Antwort sehen können. Öffnen Sie diesen Endpunkt in der API-Konsole

Details

How long the hosting platform caches the site's assets, every asset class the vendor reported, and its cacheability report for the URLs it has seen. ⛔ This is the **server-side** cache on the package itself, not `getSiteCdn` — that resource is our own Cloudflare/Bunny/CDN77 tier picker and answers about a pool zone. Conflating the two is exactly how a purge button came to call a Cloudflare path for a site whose edge is the vendor's. `permitted` and `purge_permitted` are two fields rather than one because they are two facts: the purge was measured working on a package whose cache settings and report the vendor refuses. `reported` carries every class the vendor named, including the five that cannot be written — a client renders those read-only, because writing them deletes them. Each `reasons` entry is a stable identifier (`set_cookie`, `cache_control`, …) that the client localises; no vendor prose reaches a customer through this resource. `404` for a site with no vendor hosting package, or one that is not the caller's. Requires `sites.view` — how long a site caches its CSS is the same class of fact as the rest of the Hosting tab.

Parameter

NameTypErforderlichWas es ist
siteId (path)UuidJaSite ID (UUIDv7).

Antwort

NameTypErforderlichWas es ist
permittedbooleanJaWhether the package type exposes cache settings and the report at all.
purge_permittedbooleanJaWhether a purge is permitted. Separate from `permitted` on purpose: the purge was measured working on a package whose cache settings and report the vendor refuses.
css_secondsintegerJaHow long stylesheets are cached.
image_secondsintegerJaHow long images are cached.
javascript_secondsintegerJaHow long scripts are cached.
reportedobjectJaEvery asset class the vendor reported, keyed by its own name, including the classes that cannot be written. ⛔ Read-only on a client: writing them deletes them, because the vendo…
report_availablebooleanJaWhether the cacheability report could be read. False renders an explanation rather than an empty table, so "nothing has been seen yet" and "not part of this plan" never look ide…
reportSiteCacheReportRow[]JaWhat the platform did with the URLs it has seen.

Fehler, die dieser Endpunkt zurückgeben kann

401 · 403 · 404 · 422 · 429 · 503