Rename a channel address or move it to a path

One endpoint, POST /api/admin/domains/{hostname}/rename with {new_hostname}, covers four different moves depending on what new_hostname resolves to. The panel picks the right one for you; this page explains what each does under the hood.

Plain rename

new_hostname names a host that isn't a Domain you (or anyone) already have — a straight rename. This cascades the hostname across roughly 19 tables in one transaction: buttons, segments, notifications, backgrounds, of_campaigns, clicks, impressions, fan_source, fan_link, traffer_payout, creator_links, and more — anything keyed by the old hostname now points at the new one. Local asset directories (notification media, backgrounds) are moved on disk, and both the draft and published runtime are re-exported.

Move to a path address

new_hostname is a host/slug (e.g. tease.link/mypage). The channel keeps its own hostname internally, but its public address becomes that path — a CreatorLink row is created (or reused) pointing at it, and every button/notification/segment URL that referenced the old address is rebased to the new one. 409 slug_taken if the path is already someone else's or already stands alone.

Move back to your own host

Passing the channel's own hostname back as new_hostname while it currently has a path alias drops the alias (primary_address) and rebases links back to the bare domain. 400 same_hostname if there's no alias to remove.

Move to a reserve domain (rotation)

new_hostname names another domain you already own. This isn't a rename at all — it's a full domain rotation: your config, campaigns, and money links move to that domain, and the old address starts redirecting to it. See Move off a burned domain for what that actually does and what it requires from the target domain (409 reserve_not_ready lists what's missing).

Guards that apply to all four

What's next

Renaming to swap away from an address with problems? See Check whether a domain is burning first, then Move off a burned domain.