hosting

PUT /v1/sites/{siteId}/protection/hotlink

Replace a site's hotlink-protection rules.

All hosting endpoints

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 PUT https://api.zinndigital.com/v1/sites/{siteId}/protection/hotlink \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "allow_direct": <boolean>, "allowed_hostnames": <string[]>, "extensions": <string[]> }'

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

Decides who may embed the site's files from another site. `allowed_hostnames` are the sites permitted to do so; `extensions` are the file types the rule covers; `redirect_url` is where a refused request is sent instead, and an empty string means the request is simply refused. A replace rather than a patch, for the same reason as the two block lists: the vendor endpoint replaces the set. Extensions are normalised before they are sent — a leading dot and capitals are stripped — so what the customer typed and what is enforced cannot differ. `404` for a site with no vendor hosting package. Requires `sites.view` and `sites.panel_access`.

Parameters

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).

Request body

NameTypeRequiredWhat it is
allow_directbooleanYesWhether a request with no referrer — somebody opening the file's URL directly, and every search-engine image crawler — is allowed through.
allowed_hostnamesstring[]YesThe sites permitted to embed these files. The customer's own domain is included by the vendor; list the others.
redirect_urlstringNoWhere a refused request is sent instead. Empty means the request is refused outright rather than redirected.
extensionsstring[]YesThe file extensions the rule covers, without a leading dot. An empty array means the rule covers nothing and is therefore off.

Response

NameTypeRequiredWhat it is
countriesstring[]YesThe countries in the rule, as ISO 3166-1 alpha-2 codes.
countries_allow_onlybooleanYes⛔ `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 cus…
blocked_addressesstring[]YesThe blocked addresses and CIDR ranges, canonicalised — what is here is what is in force, not what was typed.
visitor_blocking_permittedbooleanYesWhether the package type permits blocking visitors at all. One flag governs both lists.
hotlink_configuredbooleanYesWhether 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_directbooleanYesWhether 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 th…
hotlink_allowed_hostnamesstring[]YesThe sites permitted to embed these files.
hotlink_redirect_urlstringYesWhere a refused request is sent instead, or `""` when it is simply refused.
hotlink_extensionsstring[]YesThe file extensions the rule covers, normalised without a leading dot.
hotlink_permittedbooleanYesWhether the package type includes hotlink protection.
directoriesSiteProtectedDirectory[]YesThe 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 unreadabl…
password_protection_permittedbooleanYesWhether the package type includes password-protected directories.
malware_scan_permittedbooleanYesWhether the package type includes the vendor's malware scan — the capability behind `scanSite` on this deploy target.

Errors this endpoint can return

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