hosting
GET /v1/wordpress/sites/{siteId}/credentials
Who can sign in to this site's WordPress, and where.
Ìfàṣẹ́pọ̀
Fi bọ́ọ̀lù (bearer token) ranṣẹ gẹ́gẹ́ bí kọ́kọ́rọ́ API. Kọ́kọ́rọ́ náà gbọ́dọ̀ ní ìyọ̀ǹda sites.view; a ó kọ̀ ọ́ silẹ pẹlu 403, kii ṣe 404, ti kọ́kọ́rọ́ náà kò bá ní i.
Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.
Gbiyanju rẹ
Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.
curl -X GET https://api.zinndigital.com/v1/wordpress/sites/{siteId}/credentials \
-H "Authorization: Bearer zdk_live_…"Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API
Àwọn kúlẹ̀kúlẹ̀
The site's WordPress administrators — read **live** from the platform, not from the stored snapshot, because this list is what the rotate form acts on and offering a password reset for a user deleted an hour ago fails confusingly. A stale list is fine on a dashboard and wrong on a form. ⛔⛔ **There is no `password` field and there cannot be one.** WordPress stores a hash; no plaintext exists on our side or theirs. A customer copies the *username* from here and, if they need a password, mints a new one with `rotateWordPressAdminPassword`. Requires `sites.view`.
Àwọn ìpìlẹ̀
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
siteId (path) | Uuid | Bẹẹni | Site ID (UUIDv7). |
Idahun
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
admin_url | string | Bẹẹni | — |
sso_available | boolean | Bẹẹni | Whether this platform can mint a one-click login. Our own fleet writes the SSO signing key into `wp-config.php`; this platform has no shell, so it cannot — and a button offered… |
admins | WordPressAdmin[] | Bẹẹni | — |
Awọn aṣiṣe ti ibudo ipari yii le da pada
401 · 403 · 404 · 429 · 503