POST · Applications
Clone a WordPress install to a new location
Clone a WordPress install to a new location
/api/v1/wordpress/clone
Description
Returns cloned, a message, and — on success — the new install's install record. The source is install_id; the destination is target_domain (and optional target_path) on the same account. cloned:false with the reason on a node without a licensed Installatron.
Body
Send as application/json.
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response.
|
install_id
required
|
string |
The install to clone, from list_wordpress_installs (installs[].id).
|
target_domain
required
|
string |
The destination domain on the same account, e.g. staging.example.com.
|
target_path
|
string |
Up to 64 characters. Pattern ^[A-Za-z0-9._\/-]+$.
|
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.