GET /v1/wordpress/plugin-directory

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 GET https://api.zinndigital.com/v1/wordpress/plugin-directory?q=<q> \
  -H "Authorization: Bearer zdk_live_…"

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

Plugins a customer can install, from the wordpress.org directory. **Collection-level and not under a site**, because choosing a plugin comes before choosing where to put it — the fleet-wide manager picks the plugin first and the sites second, and hanging this off `/v1/sites/{siteId}/…` would force it to name an irrelevant site to search. An empty or whitespace-only `q` returns an empty page rather than the directory's popularity ranking: sixty thousand plugins nobody asked for, one upstream call per keystroke of nothing. `rating` is normalised to **0–5**. The upstream reports 0–100, and a client rendering that as stars without dividing shows every plugin as full marks. `author` is plain text — upstream sends it as an HTML anchor, which is stripped here so a vendor's markup never reaches our page. Requires `sites.view`. The upstream is unauthenticated and read-only; our egress routing for it is registered as `wordpress_org`.

Sigogi

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 429 · 503