GET /v1/sites/{siteId}/protection/file-permissions

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Ufunguo lazima uwe na ruhusa ya sites.view; ufunguo usio nayo unakataliwa kwa 403, si 404.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/protection/file-permissions \
  -H "Authorization: Bearer zdk_live_…"

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

⛔ **This `GET` RUNS the scan — it is not a cached read.** The vendor's read *is* the check, so it walks the site's filesystem. It is an explicit *"check my permissions"* action and must never fire on mount or on window focus. `check_id` is the handle the fix needs, and it is **nullable**: null means the vendor gave us no handle, so `actionable` is false and there is nothing to apply. `recommended` on each failure is nullable for the same reason — the platform sometimes names a file without naming a mode, and a guessed `644` would be applied to the customer's file. `404` for a site with no vendor hosting package. Requires `sites.view`.

Vigezo

Majibu

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 403 · 404 · 429 · 503