POST /v1/sites/{siteId}/wordpress/search-replace

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/search-replace \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "search": <string>, "replace": <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

⛔ **Destructive and irreversible from this platform.** It rewrites every occurrence in the site's database, including inside serialised values, and this platform holds no copy of what was there before. the platform returns no body, so a refusal cannot be detected after the fact — every protection is in **front** of the call: the package must carry `wp_search_replace`, WordPress must be installed, and `search` must not be blank (an empty search rewrites every row in the database, and it is refused twice — at the field and again before the vendor call). The client is required to take a typed confirmation naming the site. `202` and no body, because the rewrite continues at the vendor after the acknowledgement. `404` for a site with no vendor hosting package. Requires `sites.view` and `sites.panel_access`.

Sigogi

Jikin buƙata

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 409 · 422 · 429 · 503