hosting

GET /v1/sites/{siteId}/security/history

What the platform cleaned on a site, newest first.

All hosting endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The endpoint checks sites.view; 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}/security/history \
  -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 site's malware clean runs (newest 50): automatic cleans after a scan, Clean now runs and restores. An automatic run is recorded only when something new happened (a file cleaned or quarantined, or the first failure), so a site re-scanned daily does not grow a row per scan. sites.view; paths are relative to the document root.

Parameters

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).

Response

NameTypeRequiredWhat it is
dataMalwareCleanRun[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 429