hosting
PUT /v1/sites/{siteId}/php-version
Switch a site's PHP version.
認証
ベアラー トークンとして API キーを送信します。キーには hosting.php.manage 権限が付与されている必要があります。権限のないキーは 404 ではなく 403 で拒否されます。
このエンドポイントは組織IDを受け付けません。お使いのキーによって所属する組織がすでに特定されており、レスポンスはその組織にスコープされます。
試してみる
アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。
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コンソールでは、実際の組織IDやお客様ご自身のキーが自動入力され、ライブ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