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

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Ufunguo lazima uwe na ruhusa ya sites.panel_access; ufunguo usio nayo unakataliwa kwa 403, si 404.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

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

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

Every WordPress account on the install, with its roles and whether it is an administrator. ⛔ **This read requires `sites.panel_access`, unlike every other read on this surface**: it carries the email address of every account on the customer's site — personal data about the customer's own users — which a read-only member of the organisation has no reason to hold. The rows come from two vendor endpoints behind two different capability flags (`wp_users` and `wp_admin_users`), and what the package permits decides which halves are merged. `is_administrator` is set from the endpoint a row came from, not guessed from a role string. `404` for a site with no vendor hosting package.

Vigezo

Majibu

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 403 · 404 · 429 · 503