hosting

GET /v1/wordpress/sites/{siteId}/credentials

Who can sign in to this site's WordPress, and where.

Dhammaan hosting bixiyayaasha

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda sites.view; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

curl -X GET https://api.zinndigital.com/v1/wordpress/sites/{siteId}/credentials \
  -H "Authorization: Bearer zdk_live_…"

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Details

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

Cabiraha

MagacaNoocLoo baahan yahayMaxay tahay
siteId (path)UuidHaaSite ID (UUIDv7).

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
admin_urlstringHaa
sso_availablebooleanHaaWhether 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…
adminsWordPressAdmin[]Haa

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 429 · 503