hosting
GET /v1/sites/{siteId}/quota
Get a site's enforced disk and inode ceilings, and its usage against them.
Аутентификација
Пошаљите API кључ као bearer токен. Кључ мора имати дозволу sites.view; кључ без ње се одбија уз 403, а не 404.
Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.
Испробајте
Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/quota \
-H "Authorization: Bearer zdk_live_…"Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом 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, that counts toward the limit. Null when the platform reports no figures. Our own WordPress plugins are not included (see own_plugins_mb). |
own_plugins_mb | integer | Не | MB held by our own WordPress plugins on this site, which do NOT count toward the disk limit (owner ruling 2026-10-01). Only a plugin folder whose files are exactly a build we… |
own_plugins_inodes | integer | Не | Files and directories of our own WordPress plugins on this site, which do NOT count toward the file (inode) limit. Same verification as own_plugins_mb. |
own_plugins | string[] | Не | The plugin folders that were verified as ours and are not counted. |
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 that count toward the limit (our own WordPress plugins are not included; see own_plugins_inodes). |
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