GET /v1/wordpress/plugin-directory

Autentifikacija

Pošaljite API ključ kao nosivi token. Ključ mora imati dozvolu sites.view; ključ bez nje se odbija s kodom 403, a ne 404.

Ova krajnja točka ne prihvaća ID organizacije. Vaš ključ već identificira organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.

curl -X GET https://api.zinndigital.com/v1/wordpress/plugin-directory?q=<q> \
  -H "Authorization: Bearer zdk_live_…"

Prijavljeni ste? API konzola na vašoj nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli

Pojedinosti

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.

Parametri

Odgovor

Pogreške koje ova krajnja točka može vratiti

401 · 403 · 429 · 503