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

ማረጋገጫ

የAPI ቁልፉን እንደ bearer token ይላኩ። ቁልፉ የsites.view ፈቃድ ሊኖረው ይገባል፤ ይህ ፈቃድ የሌለው ቁልፍ በ404 ሳይሆን በ403 ውድቅ ይደረጋል።

ይህ ኤንድፖይ መክፈቻ (endpoint) የድርጅት መታወቂያ (organisation id) አይወስድም። የእርስዎ ቁልፍ (key) እሱ የሚመለከተውን ድርጅት አስቀድሞ ይለያል፣ እና ምላሹም ለዚሁ የተወሰነ ነው።

ሞክሩት

በቅንፍ ውስጥ ያለውን ማንኛውንም ነገር በራስዎ እሴቶች ይተኩ፣ እና ቁልፍ ቦታ ያዢውን ከዳሽቦርድዎ በመጣ ቁልፍ ይተኩ።

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/wordpress/activity \
  -H "Authorization: Bearer zdk_live_…"

ገብተዋል? የመቆጣጠሪያ ማዕከልዎ ውስጥ ያለው የኤፒአይ ኮንሶል ትክክለኛውን የድርጅት መታወቂያዎን እና የራስዎን ቁልፍ ይሞላል፣ እና ትክክለኛውን ምላሽ ማየት እንዲችሉ ጥያቄውን በቀጥታ ከሚሰራው ኤፒአይ ጋር ያካሂደዋል። ይህን ኤንድፖይንት በAPI ኮንሶል ውስጥ ይክፈቱ

ዝርዝሮች

Every change this platform made to the site's WordPress — plugins and themes installed, activated, updated or deleted, users created and demoted, core updates, search-replaces, maintenance mode, console commands and update-policy changes — newest first. ⛔ Bounded twice, and both bounds are returned rather than assumed: a `window_days` window and a row `limit`. `AuditLog` is time-partitioned, so the window keeps the query off every historical partition and the limit keeps one very busy site from returning a response nobody can render. A screen that showed rows without stating the window would read as *"this is everything"*. ⛔ `action` is a stable **code**, never a sentence — the client owns the wording, in every locale. `detail` carries the names of what changed and never a password, console output or an uploaded archive. Requires `sites.view`.

መለኪያዎች

ምላሽ

ይህ ማብቂያ ሊመልሳቸው የሚችሉ ስህተቶች

401 · 403 · 404 · 429 · 503