hosting
POST /v1/sites/{siteId}/protection/file-permissions
Apply the vendor's recommended permissions on a site.
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}/protection/file-permissions \
-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
Changes file modes on the customer's **live** files to the vendor's own recommendation. ⛔ **It takes no body, and that is the security property.** The check is re-run inside the same vendor conversation and the recommendation is applied against the handle that conversation just produced, so a stale `check_id` from a client cannot be replayed against files that have changed since. The only defensible input to an operation that alters file modes is the number the platform running it published moments ago. A report with nothing to fix is a `422` refusal rather than a silent success: *"we changed nothing"* and *"there was nothing to change"* are different sentences, and only one of them is reassuring. Files the vendor named without naming a mode are skipped, never sent with a guess. `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 |
|---|---|---|---|
check_id | integer | Yes | The vendor's handle for this check. **Null** when the vendor gave us none, in which case there is nothing to apply and `actionable` is false. ⛔ A client never sends it back: `fi… |
public_html_wrong | boolean | Yes | Whether the document root's own mode is wrong. |
root_wrong | boolean | Yes | Whether the package root's own mode is wrong. |
failures | SitePermissionFailure[] | Yes | The individual files the check flagged. |
actionable | boolean | Yes | Whether *Fix these* can do anything: a live check handle **and** something to fix. Its own field so the button is not offered against a report that can only be refused. |
Errors this endpoint can return
401 · 403 · 404 · 409 · 422 · 429 · 503