WordPress

Test a risky change safely: snapshot → staging copy → change → php -l → health → browser comparison → waits for approval. Kinds: plugin_update, theme_update, core_update, file_edit (a theme or plugin file), settings (allow-listed core options). Answers right away (202)

post/projects/{projectId}/wordpress/changes

Request

  • Base URL: https://hostingsurge.com/api/v1
  • URL: https://hostingsurge.com/api/v1/projects/{projectId}/wordpress/changes
  • Auth: one of:
    • HTTP bearer
    • API key in cookie __Host-hs_session

Path parameters

projectIdstring uuid required

Request body

OR
OR
OR
OR

Response

Started

idstring uuid required
projectIdstring uuid required
kind'plugin_update' | 'theme_update' | 'core_update' | 'file_edit' | 'settings' required
titlestring required
status'queued' | 'snapshotting' | 'cloning' | 'applying' | 'testing' | 'awaiting_approval' | 'deploying' | 'verifying' | 'deployed' | 'rolling_back' | 'rolled_back' | 'rollback_failed' | 'failed' | 'rejected' | 'canceled' required
stepDetailstring nullable required
inputobject required

What was asked (a file edit's text is left out: contentBytes instead)

canApproveboolean required

Waiting for approval and every required check passed

approvalCodestring nullable

Shown only to an owner or admin signed in to the dashboard: what an API key or AI agent must pass as confirm to approve

createdAtstring required

ISO-8601 timestamp

createdBystring uuid nullable required
approvedAtstring nullable required

ISO-8601 timestamp

approvedBystring uuid nullable required
finishedAtstring nullable required

ISO-8601 timestamp

updatedAtstring required

ISO-8601 timestamp

Changes

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