Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати hosting.php.manage бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

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> }'

Воarid шудаед? Консоли 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).

Ҷисми дархост

НомНамудТалаб карда мешавадИн чӣ аст
versionstringБалеA version offered for the site's product line (or the site's current one).

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
versionstringБалеThe site's effective PHP version (its own, or its line's default).
availablestring[]Бале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).
appliedbooleanНе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