hosting
POST /v1/sites/{siteId}/protection/file-permissions
Apply the vendor's recommended permissions on a site.
Pengesahan
Hantar kunci API sebagai token pembawa. Kunci tersebut mesti membawa kebenaran sites.view; kunci yang tidak mempunyainya akan ditolak dengan 403, bukan 404.
Titik akhir ini tidak memerlukan id organisasi. Kunci anda telah mengenal pasti organisasi kepunyaannya, dan respons dis skopkan kepadanya.
Cuba
Gantikan apa sahaja di dalam kurungan sudut dengan nilai anda sendiri, dan pemegang tempat kunci dengan kunci dari papan pemuka anda.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/protection/file-permissions \
-H "Authorization: Bearer zdk_live_…"Sudah log masuk? Konsol API dalam papan pemuka anda mengisi id organisasi sebenar dan kunci anda sendiri, serta menjalankan permintaan terhadap API langsung supaya anda boleh melihat respons sebenar. Buka penamat ini dalam konsol API
Butiran
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`.
Parameter
| Nama | Jenis | Diperlukan | Apakah ia |
|---|---|---|---|
siteId (path) | Uuid | Ya | Site ID (UUIDv7). |
Respons
| Nama | Jenis | Diperlukan | Apakah ia |
|---|---|---|---|
check_id | integer | Ya | 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 | Ya | Whether the document root's own mode is wrong. |
root_wrong | boolean | Ya | Whether the package root's own mode is wrong. |
failures | SitePermissionFailure[] | Ya | The individual files the check flagged. |
actionable | boolean | Ya | 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. |
Ralat yang boleh dikembalikan oleh titik akhir ini
401 · 403 · 404 · 409 · 422 · 429 · 503