hosting
POST /v1/sites/{siteId}/wordpress/users
Create an account on a site's WordPress.
Authenticatie
Stuur een API-sleutel mee als bearer token. De sleutel moet over de permissie sites.view beschikken; een sleutel zonder deze permissie wordt geweigerd met een 403 in plaats van een 404.
Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.
Probeer het
Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/users \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "login": <string>, "email": <string>, "display_name": <string>, "password": <string> }'Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console
Details
Adds a WordPress account. **The caller chooses the password** and it travels in the request only: it is never echoed in the response, never written to our records and never logged. `login` and `email` are checked against WordPress's own rules here, so the customer gets our sentence about a field they can see rather than WordPress's about one they cannot. Refused `422` when the package type does not carry `wp_users`, or when WordPress is not installed. `404` for a site with no vendor hosting package. Requires `sites.view` and `sites.panel_access`.
Parameters
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
siteId (path) | Uuid | Ja | Site ID (UUIDv7). |
Aanvraaglichaam
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
login | string | Ja | The account's login name. WordPress caps `user_login` at 60 characters and rejects anything outside this character set, so both are enforced here rather than surfaced as a vendo… |
email | string | Ja | The account's email address. |
display_name | string | Ja | The name shown on the site's posts and comments. |
password | string | Ja | The account's password. Write-only: it is accepted here and appears in no response, no log line and no error body. |
role | string | Nee | The role to create the account in — any role `listSiteWordPressRoles` reports for this install. Omit it (or send `""`) for the platform's default, which is what a vendor with no… |
Reactie
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
id | string | Ja | The account's WordPress id, carried as a string because it is the vendor's identifier rather than ours. |
login | string | Ja | The name the account signs in with. |
display_name | string | Ja | The name shown on the site's posts and comments. |
email | string | Ja | The account's email address. Personal data about the customer's **own** users, which is why the whole listing is gated on `sites.panel_access`. |
roles | string | Ja | The account's roles, in the vendor's own spelling. |
registered_at | string | Ja | When WordPress recorded the account, in the vendor's own format. Not typed as a date-time: the platform does not guarantee one, and coercing it would invent precision. |
is_administrator | boolean | Ja | Whether the account is an administrator. ⛔ Set from **which vendor endpoint the row came from**, not guessed from the role string — the two lists sit behind two different capabi… |
Fouten die dit eindpunt kan retourneren
401 · 403 · 404 · 409 · 422 · 429 · 503