Spaces

Run a WP-CLI command against a space

Runs one wp command against the space's own WordPress and waits for it to finish. This is the escape hatch beneath the named surfaces: anything WP-CLI can do that Spacefast has not given its own route. args is an already-split argument vector (["option", "get", "blogname"]), relayed verbatim — no shell parses it, so nothing re-splits or re-globs what you send. Requires write access to the space, because a wp command has unrestricted authority over the site's data, and every run is written to the space's activity trail. Note that the provider runs this as a job and reports only whether WP-CLI exited zero: output is null because the runtime exposes no channel carrying the command's own stdout.

post/v1/spaces/{spaceId}/wp-cli

Request

  • Base URL: https://api.spacefast.com
  • URL: https://api.spacefast.com/v1/spaces/{spaceId}/wp-cli
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

spaceIdstring required

Request body

argsstring[] required
mode'full' | 'limited'

Response

Response for status 200

$schemastring uri

Canonical JSON Schema URL for this response body. The server also sends it in the Link: rel="describedby" response header.

Changes

No recorded changes to this operation across all 1 revision of this API.