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

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

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

ລອງໃຊ້ເບິ່ງ

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

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

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

ລາຍລະອຽດ

Adds one subdomain to the package. The effective ceiling is applied before the vendor is called: a package type that does not permit subdomains, and a customer who has used the last of their allowance, are both 422 with a sentence they can act on. ⛔ The response is the row the platform stored, not the name that was requested — the vendor normalises and namespaces it, so the client shows what came back. ⚖️ On our own fleet this spends one of the plan's site slots (owner ruling 2026-09-01), so the refusal at the cap is the same event as it is on site create and carries the same SITE_QUOTA_EXCEEDED code and figures. The row comes back pending: the DNS record, the virtual host and the chosen stack are built by a durable workflow, and the row reaches active when the name is serving. A build that cannot be done — a hostname whose DNS we do not control, or one this server's certificate cannot cover — lands in failed with the reason in status_detail. 404 for a site with no managed hosting package and no own-fleet placement. Requires sites.view and sites.panel_access.

ພາຣາມິເຕີ

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

ເນື້ອຫາຂອງຄຳຮ້ອງ

ຊື່ປະເພດຕ້ອງການສິ່ງທີ່ມັນເປັນ
namestringແມ່ນແລ້ວThe subdomain to add. What the vendor actually created comes back in SiteSubdomain.name, and that — never this — is what the client shows.
stack_typestring<static, php, wordpress, woocommerce>ບໍ່What the subdomain should run. ⚖️ Owner ruling 2026-09-01 — a new subdomain "will start as whatever they select". static and php give an empty document root to upload or…

ຖືກໂຈະ

ຊື່ປະເພດຕ້ອງການສິ່ງທີ່ມັນເປັນ
namestringແມ່ນແລ້ວThe subdomain as the platform stored it. ⛔ Not necessarily what was requested — a vendor normalises it, and the client shows this value.
document_rootstringແມ່ນແລ້ວThe folder it serves. Relative to the package root on a resold package; an absolute path on our own fleet, where it is read back from the server's own configuration rather than…
stack_typestringບໍ່What this subdomain runs, as the customer chose at creation. ⛔ Empty on a resold package, where the folder is the vendor's and there is no stack we chose — deliberately blank…
statusstring<pending, active, failed, deleting, >ບໍ່Where the build has got to. pending while the record, the virtual host and the stack are being put in place; active once the name serves; deleting after a delete, when the…
status_detailstringບໍ່Why it failed, or a note about a build that partly succeeded — a sentence written for the customer. Empty on a healthy row.

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

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