POST /v1/sites/{siteId}/wordpress/themes

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin sites.view; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/themes \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

Installs a theme, from the wordpress.org directory by slug (what searchWordPressThemeDirectory returns) or from a zip the customer uploads. ⛔⛔ This did not exist until W22-D, and its absence is the whole of the owner's complaint on 2026-08-16: "no way in this or the main site manager bit to add new theme or uplaod one". The platform could list, activate and delete a theme and had no way to put one on a site, so a customer could only ever choose among the three themes WordPress ships with — and could delete two of them. ⛔ Exactly one of slug and zip — never both, refused rather than resolved by precedence. ⛔ activate defaults to false here and to true on the plugin path, and the asymmetry is deliberate. Activating a plugin adds behaviour; activating a theme replaces what every visitor sees, immediately, on a live site. A customer uploading a theme to look at it must not have their shop re-skinned as a side effect of the upload. ⚠️ An uploaded zip is the customer's own code running on their own site, and we do not review it. It is size-capped at 96 MiB (themes run larger than plugins — commercial multipurpose themes ship demo imagery) and rejected unless it is a valid archive containing a single top-level directory whose style.css carries a Theme Name: header, which is what WordPress itself requires. Note that a theme is not validated the way a plugin is: a block theme can legitimately contain no PHP at all, so a PHP-file check would refuse valid modern themes. ⛔ Fleet only. this platform exposes no theme-install endpoint at any path, and its own control panel offers no install control on its Themes page either — both measured 2026-08-16. So this is refused on the managed hosting line, where wp_theme_install is false; the capability map on getSiteWordPress says so up front rather than letting the customer discover it by pressing the button. Requires sites.view and sites.panel_access.

Sigogi

Jikin buƙata

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 413 · 422 · 429 · 503