Describe catalog usage
Changed onReturns physical bytes stored by one Tower-managed catalog, including Iceberg metadata and not-yet-compacted snapshot history. Measurements are cached and may be temporarily unavailable; measured_at is null when no measurement exists. BYO and S3 Tables catalogs are not metered.
get/catalogs/{name}/usage
Request
- Base URLhttps://api.tower.dev/v1
- Auth
- HTTP bearer
- or API key in header X-API-Key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
namestring required
The name of the catalog.
Query parameters
environmentstring
Environment whose catalog usage to return. When it has no same-named catalog, usage for the catalog from default is returned instead.
Response
OK
Example response
{
"$schema": "https://api.tower.dev/v1/schemas/DescribeCatalogUsageResponse.json"
}Changes
- info
added the required property
to the response with the status
- info