hosting
GET /v1/sites/{siteId}/quota
Get a site's enforced disk and inode ceilings, and its usage against them.
ການພິສູດຕົວຕົນ
ສົ່ງລະຫັດ API ເປັນ bearer token. ລະຫັດຕ້ອງມີສິດ sites.view; ລະຫັດທີ່ບໍ່ມີສິດດັ່ງກ່າວຈະຖືກປະຕິເສດດ້ວຍລະຫັດ 403, ບໍ່ແມ່ນ 404.
ຈຸດເຊື່ອມຕໍ່ນີ້ບໍ່ໄດ້ຮັບ ID ອົງກອນ. ລະຫັດຂອງທ່ານໄດ້ລະບຸອົງກອນທີ່ມັນຂຶ້ນກັບແລ້ວ, ແລະ ຄໍາຕອບແມ່ນຖືກຈໍາກັດຂອບເຂດໄວ້ສໍາລັບອົງກອນນັ້ນ.
ລອງໃຊ້ເບິ່ງ
ປ່ຽນແທນທຸກຢ່າງທີ່ຢູ່ໃນວົງເລັບມຸມດ້ວຍຄ່າຂອງທ່ານເອງ, ແລະ ປ່ຽນແທນຕົວແທນບ່ອນວ່າງຄີດ້ວຍຄີຈາກແຜງຄວບຄຸມຂອງທ່ານ.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/quota \
-H "Authorization: Bearer zdk_live_…"ເຂົ້າສູ່ລະບົບແລ້ວບໍ? ໂຄງສົນທະນາ API ໃນໜ້າັດສະຫຼອງຂອງທ່ານຈະຕື່ມຂໍ້ມູນລະຫັດອົງກອນຕົວຈິງ ແລະ ລະຫັດລັບສ່ວນຕົວຂອງທ່ານໂດຍອັດຕະໂນມັດ, ແລະ ປະຕິບັດການຮ້ອງຂໍຜ່ານ API ຕົວຈິງ ເພື່ອໃຫ້ທ່ານສາມາດເຫັນຜົນຕອບຮັບທີ່ແທ້ຈິງໄດ້. ເປີດຈຸດສິ້ນສຸດນີ້ໃນຄອນໂສລ API
ລາຍລະອຽດ
The limits the platform actually enforces on this site and what it is using against them. On our own fleet the disk and inode caps are a real, kernel-enforced setquota applied at provision time (ADR 0013 §5), and until this endpoint they were applied and exposed nowhere — a site could hit an inode or disk cap and the customer's only signal was writes beginning to fail. Every field is nullable and each null is meaningful. A null limit means no ceiling is enforced — never "unlimited" as a selling point and never "we did not look". db_limit_mb is null on every box we operate: MySQL Governor is not installed and an account's MySQL datadir lives outside its home, so no quota reaches it; database size is therefore reported as usage with no cap rather than a limit we do not apply. A site whose platform reports no ceilings at all answers 200 with every field null, not 404 — "we do not cap this" is a real answer. Requires sites.view.
ພາຣາມິເຕີ
| ຊື່ | ປະເພດ | ຕ້ອງການ | ສິ່ງທີ່ມັນເປັນ |
|---|---|---|---|
siteId (path) | Uuid | ແມ່ນແລ້ວ | Site ID (UUIDv7). |
ຖືກໂຈະ
| ຊື່ | ປະເພດ | ຕ້ອງການ | ສິ່ງທີ່ມັນເປັນ |
|---|---|---|---|
disk_used_mb | integer | ແມ່ນແລ້ວ | Disk in use, in MB. Null when the platform reports no figures. |
disk_limit_mb | integer | ແມ່ນແລ້ວ | The enforced disk ceiling in MB, or null when no cap is enforced. On our fleet this is the hard limit setquota applies — the number at which the kernel starts refusing writes,… |
inodes_used | integer | ແມ່ນແລ້ວ | Files and directories in use. |
inodes_limit | integer | ແມ່ນແລ້ວ | The enforced inode ceiling, or null when none is. A site can exhaust this while well under its disk cap — a WordPress install with a large media library or an unbounded cache… |
db_used_mb | integer | ແມ່ນແລ້ວ | Total size of the site's database, in MB. |
db_limit_mb | integer | ແມ່ນແລ້ວ | The site's database allowance in MB (W43-78). No server can hold a database to a size, so this is NOT a ceiling written to the box: it is the per-site limit the platform sweeps… |
disk_allowance_gb | integer | ແມ່ນແລ້ວ | What the site's plan grants, in GB — as opposed to disk_limit_mb, which is what the box is enforcing right now. They agree on a healthy site; a gap between them is the only… |
inodes_allowance | integer | ແມ່ນແລ້ວ | The file-and-directory allowance the site's plan grants. Null when the plan states none — which is every managed hosting plan, because this platform models no inode limit at… |
disk_allowance_authority | string<plan, per_site> | ແມ່ນແລ້ວ | Who decides this site's disk ceiling, and therefore how to read a gap between disk_allowance_gb and disk_limit_mb (D10470). plan — the plan's grant is authoritative, so… |
inodes_allowance_authority | string<plan, per_site> | ແມ່ນແລ້ວ | The same question for the file-and-directory ceiling. See disk_allowance_authority; the two are answered by one predicate so the write path and this read path cannot drift… |
ຂໍ້ຜິດພາດທີ່ຈຸດເຊື່ອມຕໍ່ນີ້ສາມາດສົ່ງຄືນໄດ້
401 · 403 · 404 · 429 · 503