hosting

PUT `/v1/sites/{siteId}/wordpress/users/{wpUserId}/password`

Set a WordPress account's password.

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 PUT https://api.zinndigital.com/v1/sites/{siteId}/wordpress/users/{wpUserId}/password \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "password": <string> }'

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

Replaces the account's password with the one in the body. It has **its own path** rather than being a field on the user resource, for the same reason the destructive staging operations have theirs: a password reset and a delete must not be two shapes of one request. `204` and no body — there is nothing to return that is not either already known or a credential. The password is write-only: accepted here, echoed nowhere. `404` for a site with no vendor hosting package, and for an id that is not on it. Requires `sites.view` and `sites.panel_access`.

Parameters

Name	Type	Required	What it is
`siteId (path)`	`Uuid`	Yes	Site ID (UUIDv7).
`wpUserId (path)`	`string`	Yes	The account's WordPress id, as `listSiteWordPressUsers` reports it.

Request body

Name	Type	Required	What it is
`password`	`string`	Yes	The new password. Write-only: it appears in no response, no log line and no error body.

Errors this endpoint can return

401 · 403 · 404 · 409 · 422 · 429 · 503

PUT /v1/sites/{siteId}/wordpress/users/{wpUserId}/password