GET · Web hosting account
Read or set hotlink protection
Read or set hotlink protection
/api/v1/hosting/hotlink-protection
This scope is inferred from the method and the endpoint's group — the OpenAPI document does
not carry one per operation. The wire is authoritative; whoami reports what your
token actually holds.
Description
GET returns {enabled, extensions[], allowedReferrers[]} (or {supported:false} where the node does not expose it). PUT takes enabled and optional comma-separated extensions, preserves the account's own referrer domains, and returns the state read back.
Query parameters
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response.
|
enabled
|
boolean | |
extensions
|
string |
Up to 255 characters. Pattern ^[A-Za-z0-9,]+$.
|
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.