hosting
GET /v1/sites/{siteId}/quota
Get a site's enforced disk and inode ceilings, and its usage against them.
Authenticatie
Stuur een API-sleutel mee als bearer token. De sleutel moet over de permissie sites.view beschikken; een sleutel zonder deze permissie wordt geweigerd met een 403 in plaats van een 404.
Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.
Probeer het
Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/quota \
-H "Authorization: Bearer zdk_live_…"Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console
Details
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`.
Parameters
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
siteId (path) | Uuid | Ja | Site ID (UUIDv7). |
Reactie
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
disk_used_mb | integer | Ja | Disk in use, in MB. Null when the platform reports no figures. |
disk_limit_mb | integer | Ja | 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 | Ja | Files and directories in use. |
inodes_limit | integer | Ja | 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 | Ja | Total size of the site's database, in MB. |
db_limit_mb | integer | Ja | 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 | Ja | 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 | Ja | 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> | Ja | **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> | Ja | 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… |
Fouten die dit eindpunt kan retourneren
401 · 403 · 404 · 429 · 503