Copy one domain's settings to another
A new or spare domain gets the same buttons, notification, and background without rebuilding by hand.
Four endpoints copy configuration from one domain (source) onto another — useful for a freshly
connected domain, a rotation reserve you're prepping ahead of time, or keeping a fleet of pages
in sync.
Copy one piece at a time
POST /api/admin/domains/{hostname}/copy-from{source}— buttons and segments, replacing whatever the target already had.POST /api/admin/domains/{hostname}/copy-notification-from{source}— the push-style notification config and its media assets (avatar, sound).POST /api/admin/domains/{hostname}/copy-bg-from{source}— the background.
{hostname} in the path is the target; source in the body is where the config comes from.
Copy several pieces onto several domains at once
POST /api/admin/bulk/copy-content with {source, targets: [...], parts: [...]} fans the
same copy out to a whole list of domains. parts is any of buttons_segments, bg,
notification, canvas_color. Each target is handled independently — one target failing (e.g.
a target that no longer exists) doesn't stop the others; the response lists per-target
{host, ok, detail} so you can see exactly which ones landed.
Every copy lands in draft state only. The target won't show the new buttons/notification/ background to visitors until you publish it, same as any other draft edit.
Don't pre-copy buttons onto a domain you're holding in reserve for a rotation — rotation requires the reserve to be empty (no buttons, links, or campaigns of its own yet). Rotate first, then copy settings onto the domain once it's already carrying the traffic.
What's next
Getting a fresh domain ready to take over? See Move off a burned domain for what a reserve needs before it can be rotated into.