POST /v1/wordpress/refresh

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/wordpress/refresh \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "site_ids": <string[]> }'

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

Collects up to 25 sites' WordPress posture from their platforms. ⛔ Capped because each site is a real vendor conversation, and a customer with four hundred sites pressing *"refresh everything"* must not be able to turn their own screen into a rate-limit incident. ⛔ **One site's failure never fails the call.** The response reports per site, because the interesting answer on an estate is usually *"eleven collected and one refused, here is which"* — and a 4xx for the whole batch would hide it. A site outside the caller's scope comes back `skipped`, never `404`, so this can never confirm whether a foreign site id exists. Requires `sites.view` **and** `sites.panel_access`.

Jikin buƙata

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 422 · 429