hosting
GET /v1/sites/{siteId}/quota
Get a site's enforced disk and inode ceilings, and its usage against them.
Pagpapatotoo
Magpadala ng API key bilang isang bearer token. Kailangang taglayin ng key ang pahintulot na sites.view; ang key na wala nito ay tatanggihan gamit ang 403, hindi 404.
Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.
Subukan ito
Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/quota \
-H "Authorization: Bearer zdk_live_…"Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API
Mga Detalye
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`.
Mga Parameter
| Pangalan | Uri | Kailangan | Ano ito |
|---|---|---|---|
siteId (path) | Uuid | Oo | Site ID (UUIDv7). |
Tugon
| Pangalan | Uri | Kailangan | Ano ito |
|---|---|---|---|
disk_used_mb | integer | Oo | Disk in use, in MB. Null when the platform reports no figures. |
disk_limit_mb | integer | Oo | 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 | Oo | Files and directories in use. |
inodes_limit | integer | Oo | 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 | Oo | Total size of the site's database, in MB. |
db_limit_mb | integer | Oo | 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 | Oo | 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 | Oo | 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> | Oo | **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> | Oo | 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… |
Mga error na maibabalik ng endpoint na ito
401 · 403 · 404 · 429 · 503