hosting
GET /v1/sites/{siteId}/wordpress/update-policy
What this site is set to update by itself, and where it has drifted.
احراز هویت
یک کلید API را به عنوان یک توکن حامل ارسال کنید. این کلید باید دارای مجوز sites.view باشد؛ کلیدی که فاقد آن باشد با خطای 403 رد میشود، نه 404.
این نقطه پایانی هیچ شناسه سازمانی را دریافت نمیکند. کلید شما در حال حاضر سازمان مربوطه را مشخص میکند و پاسخ در همان محدوده ارائه میشود.
امتحان کنید
هر چیزی را که داخل براکتهای زاویهدار قرار دارد با مقادیر خودتان جایگزین کنید، و نگهدارنده کلید را با کلیدی از داشبورد خود جایگزین نمایید.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/wordpress/update-policy \
-H "Authorization: Bearer zdk_live_…"وارد شدهاید؟ کنسول API در داشبورد شما شناسه سازمان واقعی و کلید خودتان را پر میکند و درخواست را روی API زنده اجرا میکند تا بتوانید پاسخ واقعی را ببینید. این نقطه پایانی را در کنسول API باز کنید
جزئیات
Returns three things that must never be collapsed into one: the policy an operator stored, what the site is actually configured to do, and the drift between them. ⛔ A screen showing only the stored policy cannot tell a customer that the policy was never applied — which is the whole point. A decision is applied when a row changes, and the row that decides whether a WordPress updates itself lives on that WordPress, not in this platform's database. A customer can change any of it from wp-admin, a plugin can change it on activation, and a restored backup carries the old settings back. ⛔ observed_core is "" when WP_AUTO_UPDATE_CORE is not defined at all, which is NOT the same as off — an undefined constant means WordPress applies its own default, which is minor. Rendering the first as the second would tell an operator their sites are not taking security releases when in fact they are. ⛔ observed_read is false when the site could not be read (a managed hosting package, or a box that did not answer). An empty drift is only meaningful while it is true; otherwise an unreachable site renders as compliant, which is the worst default for a security setting. Ungated read — requires sites.view.
پارامترها
| نام | نوع | الزامی | چیست |
|---|---|---|---|
siteId (path) | Uuid | بله | Site ID (UUIDv7). |
پاسخ
| نام | نوع | الزامی | چیست |
|---|---|---|---|
core | string<off, minor, all> | بله | The stored policy for WordPress core updates. |
plugins | boolean | بله | The stored policy — whether every plugin should auto-update. |
themes | boolean | بله | The stored policy — whether every theme should auto-update. |
ring | string<canary, early, general> | بله | The staged-rollout ring this site belongs to. |
applied_at | string | بله | When the policy last reached the site, ISO-8601, or "" if it never has. ⛔ A timestamp and not a flag: "when did this last reach the site" is the question an operator asks, and a… |
apply_error | string | بله | Why the last apply failed, or "". Kept beside applied_at rather than replacing it, so a failed re-apply does not erase that an earlier one worked. |
observed_read | boolean | بله | Whether the site itself was read. ⛔ An empty drift is only meaningful while this is true. |
observed_core | string | بله | What WP_AUTO_UPDATE_CORE is set to on the site — off, minor, all, or "" meaning the constant is not defined at all, so WordPress applies its own default. ⛔ "" is… |
plugins_off | string[] | بله | The plugins on this site that are NOT auto-updating. |
themes_off | string[] | بله | The themes on this site that are NOT auto-updating. |
drift | string<core, plugins, themes>[] | بله | Which of core, plugins, themes the site disagrees with the policy about. |
خطاهایی که این نقطه پایانی میتواند برگرداند
401 · 403 · 404 · 429 · 503