hosting
GET /v1/sites/{siteId}/quota
Get a site's enforced disk and inode ceilings, and its usage against them.
認証
ベアラー トークンとして API キーを送信します。キーには sites.view 権限が付与されている必要があります。権限のないキーは 404 ではなく 403 で拒否されます。
このエンドポイントは組織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. 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