---
title: "Deploy Custom Domain"
method: POST
path: "/api/v1/content/properties/{property_id}/custom-domain/deploy"
tags: ["Content Management"]
---

# Deploy Custom Domain

`POST /api/v1/content/properties/{property_id}/custom-domain/deploy`

Mount this property's guide at {hostname}{path} on the hotel's own domain
by deploying a Worker into their Cloudflare zone.

This is the one route in the program that writes to customer
infrastructure, so the ordering matters: the script is uploaded and
verified before any route is attached. A route pointing at a script that
failed to upload would put the hotel's own traffic into a Worker that does
not exist.

## Path parameters

- `property_id` string, uuid, required

## Request body

- CustomDomainUpdate
  - `custom_hostname` string, required
  - `custom_path_prefix` string, nullable

## Response `200`

Successful Response

- CustomDomainResponse
  - `custom_hostname` string, nullable, required
  - `custom_path_prefix` string, nullable, required
  - `cname_target` string, nullable, required
  - `ssl_status` string, nullable
  - `cloudflare_configured` boolean

## Other responses

- `409` — Cloudflare not connected
- `422` — Malformed hostname or path, the guide's own origin, or a domain that is not in the connected Cloudflare account
- `502` — Cloudflare deployment failed

---

[API](https://skmtc.dev/getanana/apis/cleon-api.md) · [All operations](https://skmtc.dev/getanana/apis/cleon-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/getanana/cleon-api/revisions/a9141b6e4e7e/schema)