hosting

PUT `/v1/sites/{siteId}/php-version`

Switch a site's PHP version.

احراز هویت

یک کلید API را به عنوان یک توکن حامل ارسال کنید. این کلید باید دارای مجوز hosting.php.manage باشد؛ کلیدی که فاقد آن باشد با خطای 403 رد می‌شود، نه 404.

این نقطه پایانی هیچ شناسه سازمانی را دریافت نمی‌کند. کلید شما در حال حاضر سازمان مربوطه را مشخص می‌کند و پاسخ در همان محدوده ارائه می‌شود.

امتحان کنید

هر چیزی را که داخل براکت‌های زاویه‌دار قرار دارد با مقادیر خودتان جایگزین کنید، و نگهدارنده کلید را با کلیدی از داشبورد خود جایگزین نمایید.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/php-version \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "version": <string> }'

وارد شده‌اید؟ کنسول API در داشبورد شما شناسه سازمان واقعی و کلید خودتان را پر می‌کند و درخواست را روی API زنده اجرا می‌کند تا بتوانید پاسخ واقعی را ببینید. این نقطه پایانی را در کنسول API باز کنید

جزئیات

Sets the site's desired PHP version and returns 202 Accepted. The target must be a version currently offered for the site's product line (or the site's own current version); anything else is a 422. A retired version an existing site already runs is kept — this call never forces a migration. Requires hosting.php.manage. The machine serving the site is told before the row is written, on both lines: one ack-checked vendor call on the resold range, and one idempotent cloudlinux-selector set --current-version= on our own fleet. A version the machine refuses is a 422 and the row is left alone, so the platform never claims a runtime the box is not running. 202 therefore under-promises rather than over-promises. A site with no hosting vendor and no placed worker has nothing serving it yet: the desired version is recorded and provisioning applies it. The site's PHP extensions move with it. The PHP selector keeps extensions per version, so once the machine confirms the switch, the site's composed extension set is pushed for the new version: the platform floor, the customer's own toggles, and whatever its one-click application needs. Without this, a site landed on the new version's default set; a Drupal site answered 500 on every page with no dom (D24906). If that push fails, the switch still stands, and the hourly PHP-settings converge pushes the set on its next pass. A machine that cannot be reached at all — its account does not exist yet, SSH is down, the vendor is unavailable — is a 503, not a 422 and not a 500: the request was valid and a retry can succeed. The stored version is left exactly as it was, so a 503 here means nothing changed anywhere.

پارامترها

نام	نوع	الزامی	چیست
`siteId (path)`	`Uuid`	بله	Site ID (UUIDv7).

بدنه درخواست

نام	نوع	الزامی	چیست
`version`	`string`	بله	A version offered for the site's product line (or the site's current one).

پاسخ

نام	نوع	الزامی	چیست
`version`	`string`	بله	The site's effective PHP version (its own, or its line's default).
`available`	`string[]`	بله	Versions the site may switch to — those offered for its product line, plus its own current version even if that has since been retired (grandfathered).
`applied`	`boolean`	خیر	Whether the machine serving this site was actually told, and the change read back off it. Present on the `PUT` response only. `false` is not a failure: it means the site has no…

خطاهایی که این نقطه پایانی می‌تواند برگرداند

401 · 403 · 404 · 422 · 429 · 503

PUT /v1/sites/{siteId}/php-version