hosting

POST /v1/sites/{siteId}/wordpress/hardening/{check}

Apply the one-click fix for one hardening check.

All hosting endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/hardening/{check} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Writes the fix (DISALLOW_FILE_EDIT, WP_DEBUG off, FORCE_SSL_ADMIN, or fresh secret keys with wp config shuffle-salts, which signs every user out), then confirms it by re-reading the site, and audit-logs wordpress.hardening.<check>. force_ssl_admin is refused while the site address is not HTTPS (it would lock the admin out). The response is the whole checklist as re-read. ⛔ Fleet only — refused where wp_maintenance is false. Requires sites.view and sites.panel_access.

Parameters

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).
check (path)string<file_editor_disabled, debug_off, force_ssl_admin, salts_unique>YesThe check to fix — one whose fixable is true.

Response

NameTypeRequiredWhat it is
checksSiteWordPressHardeningCheck[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503