hosting

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

Set a WordPress account's password.

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

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> }'

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。在 API 控制台中打开此端点

详细信息

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`.

参数

名称	类型	必填	内容简介
`siteId (path)`	`Uuid`	是	Site ID (UUIDv7).
`wpUserId (path)`	`string`	是	The account's WordPress id, as `listSiteWordPressUsers` reports it.

请求正文

名称	类型	必填	内容简介
`password`	`string`	是	The new password. Write-only: it appears in no response, no log line and no error body.

此端点可能返回的错误

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

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