hosting

POST /v1/sites/{siteId}/wordpress/staging

Copy a site's live WordPress onto staging.

ຈຸດສິ້ນສຸດ hosting ທັງໝົດ

ເອກະສານນັກພັດທະນາທັງໝົດ

ການພິສູດຕົວຕົນ

ສົ່ງລະຫັດ API ເປັນ bearer token. ລະຫັດຕ້ອງມີສິດ sites.view; ລະຫັດທີ່ບໍ່ມີສິດດັ່ງກ່າວຈະຖືກປະຕິເສດດ້ວຍລະຫັດ 403, ບໍ່ແມ່ນ 404.

ຈຸດເຊື່ອມຕໍ່ນີ້ບໍ່ໄດ້ຮັບ ID ອົງກອນ. ລະຫັດຂອງທ່ານໄດ້ລະບຸອົງກອນທີ່ມັນຂຶ້ນກັບແລ້ວ, ແລະ ຄໍາຕອບແມ່ນຖືກຈໍາກັດຂອບເຂດໄວ້ສໍາລັບອົງກອນນັ້ນ.

ລອງໃຊ້ເບິ່ງ

ປ່ຽນແທນທຸກຢ່າງທີ່ຢູ່ໃນວົງເລັບມຸມດ້ວຍຄ່າຂອງທ່ານເອງ, ແລະ ປ່ຽນແທນຕົວແທນບ່ອນວ່າງຄີດ້ວຍຄີຈາກແຜງຄວບຄຸມຂອງທ່ານ.

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

ເຂົ້າສູ່ລະບົບແລ້ວບໍ? ໂຄງສົນທະນາ API ໃນໜ້າັດສະຫຼອງຂອງທ່ານຈະຕື່ມຂໍ້ມູນລະຫັດອົງກອນຕົວຈິງ ແລະ ລະຫັດລັບສ່ວນຕົວຂອງທ່ານໂດຍອັດຕະໂນມັດ, ແລະ ປະຕິບັດການຮ້ອງຂໍຜ່ານ API ຕົວຈິງ ເພື່ອໃຫ້ທ່ານສາມາດເຫັນຜົນຕອບຮັບທີ່ແທ້ຈິງໄດ້. ເປີດຈຸດສິ້ນສຸດນີ້ໃນຄອນໂສລ API

ລາຍລະອຽດ

This copies live onto staging and can do nothing else. It takes no body, so there is no field a caller could set to make it publish over the live site — that is publishSiteWordPressStaging, a different path with its own refusal. the platform itself distinguishes the two directions with one string in one field, which is precisely why they must not share an endpoint. An existing staging copy is overwritten by the live site: that is what "refresh my staging" means, and it is the safe direction. ⛔⛔ 202 means accepted, never finished, and a client that treats it as finished will be wrong every time. Copying a document root and a database takes far longer than any HTTP request may — ~30 s for an empty WordPress on the Zinn® fleet, and it scales with the site — so the copy runs on the platform's queue. The body carries the new entry in operations: poll getSiteWordPressStaging until it leaves queued and running, and read message if it ends failed. ⭐ Refusals still arrive here, immediately: a site whose platform cannot stage is a 422 from this call, not a failed operation a minute later. 404 for a site whose platform has no WordPress to manage. 409 when another staging operation is already running for the site. Requires sites.view and sites.panel_access.

ພາຣາມິເຕີ

ຊື່ປະເພດຕ້ອງການສິ່ງທີ່ມັນເປັນ
siteId (path)Uuidແມ່ນແລ້ວSite ID (UUIDv7).

ຖືກໂຈະ

ຊື່ປະເພດຕ້ອງການສິ່ງທີ່ມັນເປັນ
permittedbooleanແມ່ນແລ້ວWhether this site may use WordPress staging at all — on the resold range the package type's own flag, and on our own fleet the plan's staging entitlement.
publish_modesstring<files, db, both>[]ແມ່ນແລ້ວWhich publish scopes this site's platform can actually perform, for publishSiteWordPressStaging. A client offers exactly these and no more. ⛔⛔…
publishablebooleanແມ່ນແລ້ວWhether the plan also carries publish to live, which is a separate permission from creating a staging copy. ⛔ Not folded into permitted, because the catalogue sells the two…
reinstallablebooleanແມ່ນແລ້ວWhether the plan carries reinstalling the platform software over the staging copy. A fifth question for the same reason as publishable: the catalogue sells it separately, so…
idle_removal_daysintegerແມ່ນແລ້ວAfter how many days with no change a staging copy is removed automatically, or null when nothing ever removes it. ⛔⛔…
idle_notice_daysintegerແມ່ນແລ້ວHow many days' warning the customer is emailed before that removal, or null when idle_removal_days is null.
operationsSiteWordPressStagingOperation[]ແມ່ນແລ້ວThe site's recent staging operations, newest first — the client's window onto work that runs after the request returns. ⛔⛔…
dataSiteWordPressStagingClone[]ແມ່ນແລ້ວThe staging copies that exist.

ຂໍ້ຜິດພາດທີ່ຈຸດເຊື່ອມຕໍ່ນີ້ສາມາດສົ່ງຄືນໄດ້

401 · 403 · 404 · 409 · 422 · 429 · 503