hosting

POST `/v1/sites/{siteId}/protection/directories/remove`

Take the password off a folder on a site.

Kimlik Doğrulama

Bearer token olarak bir API anahtarı gönderin. Anahtar sites.view iznine sahip olmalıdır; bu izne sahip olmayan bir anahtar 404 ile değil, 403 ile reddedilir.

Bu uç nokta hiçbir organizasyon kimliği almaz. Anahtarınız zaten ait olduğu organizasyonu tanımlar ve yanıt bu organizasyonla sınırlandırılır.

Dene

Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/protection/directories/remove \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "directory": <string> }'

Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın

Ayrıntılar

Removes the folder's HTTP password. Everything in it becomes publicly readable again the moment this returns, so the client names the folder back before calling. ⛔ A POST to a /remove sub-path rather than a DELETE with the folder in the URL, and the folder travels in the body: a directory contains slashes, and a percent-encoded / inside a path segment is rejected or silently decoded by enough proxies that it is not a contract worth betting a security control on. The whole protection state comes back, so the card re-renders from the server's answer. 404 for a site with no vendor hosting package. Requires sites.view and sites.panel_access.

Parametreler

Ad	Tür	Zorunlu	Ne olduğu
`siteId (path)`	`Uuid`	Evet	Site ID (UUIDv7).

İstek gövdesi

Ad	Tür	Zorunlu	Ne olduğu
`directory`	`string`	Evet	The folder, exactly as `SiteProtection.directories` reports it. Normalised the same way on both sides, so the folder that is unprotected is the one that was named.

Yanıt

Ad	Tür	Zorunlu	Ne olduğu
`countries`	`string[]`	Evet	The countries in the rule, as ISO 3166-1 alpha-2 codes.
`countries_allow_only`	`boolean`	Evet	⛔ `true` means `countries` is an allow-list: only those countries reach the site. Its own field rather than a mode string, because inverting it inverts who can reach the…
`blocked_addresses`	`string[]`	Evet	The blocked addresses and CIDR ranges, canonicalised — what is here is what is in force, not what was typed.
`visitor_blocking_permitted`	`boolean`	Evet	Whether the package type permits blocking visitors at all. One flag governs both lists.
`hotlink_configured`	`boolean`	Evet	Whether any hotlink rule exists. ⛔ `false` means no rules have been set up — not "protection is on with no allowed hosts", which would read as a site blocking everybody.
`hotlink_allow_direct`	`boolean`	Evet	Whether a request with no referrer is allowed through. Null when the vendor did not state it — distinct from `false`, because a toggle rendered from an unknown lies about the…
`hotlink_allowed_hostnames`	`string[]`	Evet	The sites permitted to embed these files.
`hotlink_redirect_url`	`string`	Evet	Where a refused request is sent instead, or `""` when it is simply refused.
`hotlink_extensions`	`string[]`	Evet	The file extensions the rule covers, normalised without a leading dot.
`hotlink_permitted`	`boolean`	Evet	Whether the package type includes hotlink protection.
`directories`	`SiteProtectedDirectory[]`	Evet	The password-protected folders. ⛔ Read from a vendor field that documents `null` as "the request could not complete" — the opposite of "nothing is protected" — so an unreadable…
`password_protection_permitted`	`boolean`	Evet	Whether the package type includes password-protected directories.
`malware_scan_permitted`	`boolean`	Evet	Whether the package type includes the vendor's malware scan — the capability behind `scanSite` on this deploy target.

Bu uç noktanın dönderebileceği hatalar

401 · 403 · 404 · 409 · 422 · 429 · 503

POST /v1/sites/{siteId}/protection/directories/remove