# PATCH /websites/:website_id/redirect-domains/:host

**Resource:** [Websites](./websites.md)  
**MCP tool:** `update_website_redirect_domain`  
**Scopes:** `websites:write`  
**Write operation:** yes

Set or clear the landing page of an existing redirect-only domain. With landing_path set, every request for the domain lands on that one page of the website (a temporary 302), with {domain} replaced by the name the visitor typed, e.g. "/available/?domain={domain}". Send landing_path: null (or "") to clear it, so the domain goes back to keeping the visitor's own path (a permanent 301).

## Parameters

| Name | In | Type | Required | Description |
|------|----|------|----------|-------------|
| `website_id` | path | string | yes | The TARGET website the redirect domain points at. |
| `host` | path | string | yes | The redirect domain to change, e.g. "buycar.com.au". |
| `landing_path` | body | string | no | A path on the website starting with "/" that every request for the domain lands on, {domain} filled with the name the visitor typed, e.g. "/available/?domain={domain}". Send "" (or null) to clear it, so the domain keeps the visitor's own path again. This is the only field the call changes. |
| `require_approval` | body | boolean | no | Optional. Set true to route this write into the approval queue for human review instead of executing it immediately (returns 202 + an approval_id). Works even when your key/token has permission to execute directly. |

## Request example

```bash
curl -X PATCH   "https://api.trustpager.com/functions/v1/api/v1/websites/:website_id/redirect-domains/:host"   -H "Authorization: Bearer YOUR_API_KEY"   -H "Content-Type: application/json"   -d '{"landing_path":"...","require_approval":"..."}'
```

---
Base URL: `https://api.trustpager.com/functions/v1/api/v1` — Auth: `Authorization: Bearer YOUR_API_KEY`