hosting

GET /v1/sites/{siteId}/wordpress/checksum

Check a site's WordPress core files against the published checksums.

Dukkan hosting wuraren ƙarshe

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/sites/{siteId}/wordpress/checksum \
  -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

Compares the install's core files with WordPress.org's published checksums and names every file that differs. A modified core file is the classic signature of a compromise, so this is the read behind *"has anything been tampered with"*. `ok` is `true` when nothing differs. `404` for a site with no vendor hosting package. Requires `sites.view`.

Sigogi

SunaNau'iAna buƙataAbin da yake
siteId (path)UuidEhSite ID (UUIDv7).

Martani

SunaNau'iAna buƙataAbin da yake
okbooleanEhWhether nothing differs.
filesstring[]EhThe core files that differ, by path. Empty when `ok` is true. Read from the vendor's path-keyed map, so a file is named rather than merely counted.

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 429 · 503