hosting
POST /v1/sites/{siteId}/wordpress/checksum
Restore a site's modified WordPress core files.
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 POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/checksum \
-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
Asks the vendor to replace every core file that differs from the published checksum with the published one. Local modifications to core files are lost, which is the point — but a legitimate customisation living in core goes with them, so the client names the files back first. 202 and not 200: the platform restores the files afterwards, so the report in the body may still list them. A security screen that says "fixed" before it is fixed is worse than one that says "still checking". 404 for a site with no vendor hosting package. Requires sites.view and sites.panel_access.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
ok | boolean | Yes | Whether nothing differs. |
files | string[] | Yes | The core files that differ, by path. Empty when ok is true. Read from the vendor's path-keyed map, so a file is named rather than merely counted. |
Errors this endpoint can return
401 · 403 · 404 · 409 · 422 · 429 · 503