GET /v1/sites/{siteId}/wordpress/activity

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}/wordpress/activity \
  -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

Every change this platform made to the site's WordPress — plugins and themes installed, activated, updated or deleted, users created and demoted, core updates, search-replaces, maintenance mode, console commands and update-policy changes — newest first. ⛔ Bounded twice, and both bounds are returned rather than assumed: a `window_days` window and a row `limit`. `AuditLog` is time-partitioned, so the window keeps the query off every historical partition and the limit keeps one very busy site from returning a response nobody can render. A screen that showed rows without stating the window would read as *"this is everything"*. ⛔ `action` is a stable **code**, never a sentence — the client owns the wording, in every locale. `detail` carries the names of what changed and never a password, console output or an uploaded archive. Requires `sites.view`.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 429 · 503