# PUT /api/v1/hosting/hotlink-protection

> Read or set hotlink protection

- Group: hosting
- Tier: W
- Required scope: write:hosting
- Docs: https://api.inleed.com/reference/hosting/update-hotlink-protection

## 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.

## Body

- `input` — string (required). A domain, email address, website URL, or Inleed service id — for example example.se, info@example.se 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,]+$.

## Request

```bash
curl -X PUT "https://mcp.inleed.com/api/v1/hosting/hotlink-protection" \
  -H "Authorization: Bearer inl_live_…" \
  -H "Content-Type: application/json" \
  -d '{"input":"example.se","enabled":true,"extensions":"example.se"}'
```

## Errors

- **400**  — codes: invalid_request
- **401** No token was presented, or the token is revoked, expired or unknown. — codes: unauthorized, token_expired, token_revoked
- **403** The token lacks a required scope, or this account does not own the resource. — codes: insufficient_scope, domain_not_owned
- **404** No such resource for this account. — codes: not_found
- **422** Validation error — codes: validation_failed
- **429** The rate limit for this token is exhausted. See `Retry-After`. — codes: rate_limited
- **500** Something went wrong on our side. The failure is logged against `requestId`. — codes: internal_error

## Related

- GET /api/v1/hosting/hotlink-protection — https://api.inleed.com/reference/hosting/manage-hotlink-protection
- GET /api/v1/hosting — https://api.inleed.com/reference/hosting/list-hosting-accounts

