hosting
POST /v1/sites/{siteId}/wp-credentials
Generate a new WordPress admin password for a site.
Autentifikatsiya
API kalitini bearer token sifatida yuboring. Kalit sites.view ruxsatiga ega boʻlishi shart; ruxsatsiz kalit 404 emas, balki 403 xatosi bilan rad etiladi.
Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.
Sinab ko'rish
Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wp-credentials \
-H "Authorization: Bearer zdk_live_…"Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching
Tafsilotlar
Sets a new password on the server first and records it only once WordPress has it, so a failure can never leave the customer holding a password that does not open their site. Requires `sites.view` and `sites.panel_access`, and is audit-logged. Re-reads the site's admin row before resolving which user to act on. Without that step this call fails with "no such user" for exactly the customers who need it — the ones who renamed their WordPress admin outside the app — so the one action that repairs a drifted credential was the one that stopped working once there was drift to repair.
Parametrlar
| Nomi | Turi | Majburiy | Nima bu |
|---|---|---|---|
siteId (path) | Uuid | Ha | Site ID (UUIDv7). |
Javob
| Nomi | Turi | Majburiy | Nima bu |
|---|---|---|---|
site_id | Uuid | Ha | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
username | string | Ha | This site's own admin username, re-read from the site's `wp_users` row on every request. A customer who renames the account in phpMyAdmin, wp-admin or wp-cli sees the new name h… |
email | string | Ha | `wp_users.user_email` on the site itself — where a WordPress password reset would actually go. Empty until the platform has managed to read one. |
password | string | Ha | The current password, or empty when it cannot be shown — see `can_reveal`. It is derived from a platform key and the site's rotation epoch, never stored, so there is no per-site… |
can_reveal | boolean | Ha | False when the customer set their own password (nothing of ours to show) or the environment has no signing key. Rotating makes it true again. |
is_custom | boolean | Ha | The password in use was set by the customer through this app, so there is nothing of ours to show. Distinct from `changed_outside_app`. |
changed_outside_app | boolean | Ha | Proven: the password the platform holds no longer opens the site, so it was changed outside of the Zinn Digital® Hosting App — phpMyAdmin, wp-admin or wp-cli. WordPress stores `… |
checked_at | string | Ha | When the platform last managed to LOOK at the site's admin row. Null means never. |
verified_at | string | Ha | When the platform last PROVED these credentials are the live ones. Null means never. Deliberately separate from `checked_at`: "we have not been able to reach this site for a wee… |
login_url | string | Ha | Where to sign in. |
Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar
401 · 403 · 404 · 422 · 429