hosting
GET /v1/sites/{siteId}/quota
Get a site's enforced disk and inode ceilings, and its usage against them.
Hitelesítés
Küldjön egy API-kulcsot bearer tokenként. A kulcsnak rendelkeznie kell a(z) sites.view jogosultsággal; az ezzel nem rendelkező kulcsok esetén a rendszer 403-as hibát ad vissza 404 helyett.
Ez a végpont nem fogad el szervezeti azonosítót. Az Ön kulcsa már azonosítja azt a szervezetet, amelyhez tartozik, és a válasz is erre vonatkozik.
Próbálja ki
Cserélje ki a hegyes zárójelek közötti részt a saját értékeivel, a kulcshelyőrzőt pedig a vezérlőpultján található kulccsal.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/quota \
-H "Authorization: Bearer zdk_live_…"Be van jelentkezve? A vezérlőpultban lévő API-konzol kitölti a valós szervezetazonosítóját és a saját kulcsát, és a kérést az éles API-n futtatja, hogy láthassa a tényleges választ. Nyissa meg ezt a végpontot az API konzolban
Részletek
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`.
Paraméterek
| Név | Típus | Kötelező | Mi ez |
|---|---|---|---|
siteId (path) | Uuid | Igen | Site ID (UUIDv7). |
Válasz
| Név | Típus | Kötelező | Mi ez |
|---|---|---|---|
disk_used_mb | integer | Igen | Disk in use, in MB. Null when the platform reports no figures. |
disk_limit_mb | integer | Igen | 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 | Igen | Files and directories in use. |
inodes_limit | integer | Igen | 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 di… |
db_used_mb | integer | Igen | Total size of the site's database, in MB. |
db_limit_mb | integer | Igen | Always null on platforms we operate. No per-account database *size* limit is enforceable on our boxes, so this reports the absence of a cap rather than inventing one. |
disk_allowance_gb | integer | Igen | 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 onl… |
inodes_allowance | integer | Igen | 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> | Igen | **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, s… |
inodes_allowance_authority | string<plan, per_site> | Igen | 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 (#2… |
Hibák, amelyeket ez a végpont visszaadhattatlan
401 · 403 · 404 · 429 · 503