WordPress

Deploy a tested change to the live site (files and allow-listed options only, never database tables; checked afterwards and rolled back automatically on failure). Owners and admins; confirm is the change id from a dashboard session, else the approval code shown there

post/projects/{projectId}/wordpress/changes/{changeId}/approve

Request

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

Path parameters

projectIdstring uuid required
changeIdstring uuid required

Request body

confirmstring required

Dashboard: the change id. API keys and AI agents: the approval code a person reads in the dashboard

acceptVisualChangesboolean

Required when the visual comparison found changes

Response

Deploying

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.