Create or push a WordPress staging copy

POST


          /api/v1/wordpress/staging

Try it

W Write

Scope write:hosting

Description

action:create clones install_id to a staging path and returns the result immediately. action:push syncs a staging_id copy back over install_id (production) — it overwrites production, so it returns {status:"confirmation_required", confirmationUrl, …} and syncs nothing on this call; show the human the URL to approve.

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 production install, from `list_wordpress_installs` (`installs[].id`) — the clone source for `create`, the overwrite destination for `push`.
`action` required	enum	`create` to clone production to a staging copy; `push` to sync a staging copy back over production (overwrites production — confirmation-tier). One of `create`, `push`.
`staging_id`	string	Required for `push`: the staging install to sync from, from `list_wordpress_installs`.
`target_domain`	string	Optional for `create`: the domain to stage on. Omit to use the install's own domain.
`target_path`	string	Up to 64 characters. Pattern `^[A-Za-z0-9._\/-]+$`.
`attempt_key`	string	Idempotency key for this intent. Keep it stable across retries so a timed-out retry cannot buy the same thing twice. Up to 128 characters.

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.

400

invalid_request

401 No token was presented, or the token is revoked, expired or unknown.

unauthorizedtoken_expiredtoken_revoked

403 The token lacks a required scope, or this account does not own the resource.

insufficient_scopedomain_not_owned

404 No such resource for this account.

not_found

422 Validation error

validation_failed

429 The rate limit for this token is exhausted. See `Retry-After`.

rate_limited

500 Something went wrong on our side. The failure is logged against `requestId`.

internal_error