from anomalyarmor import Clientclient = Client()# By qualified name (primary)asset = client.assets.get("snowflake.prod.warehouse.orders")# By UUID (for automation)asset = client.assets.get(id="550e8400-e29b-41d4-a716-446655440000")print(asset.qualified_name, asset.row_count)
AnomalyArmor supports two ways to identify assets:
Qualified Name (Primary)
Human-readable, hierarchical identifier:
{source}.{database}.{schema}.{table}
Examples:
snowflake.prod.warehouse.orders
databricks.main.analytics.daily_sales
postgresql.app_db.public.users
Use qualified names in code for readability. They’re stable as long as you don’t rename the underlying table.
UUID (Secondary)
System-generated unique identifier. Use for automation where names may change:
550e8400-e29b-41d4-a716-446655440000
Error Responses
Status
Code
Description
404
ASSET_NOT_FOUND
Asset doesn’t exist or you don’t have access
400
VALIDATION_ERROR
Invalid qualified name format
{ "error": { "code": "ASSET_NOT_FOUND", "message": "Asset not found", "details": { "asset_id": "snowflake.prod.warehouse.orders", "suggestion": "Check the qualified name format: source.database.schema.table" } }}
Common Questions
Should I identify an asset by qualified name or UUID?
Use the qualified name (source.database.schema.table) for code and config you read by hand: it survives re-discovery and is human-debuggable. Use the UUID for automation where names might be renamed upstream, since UUIDs are stable across renames. Both identifiers work on every /api/v1/assets/{id} endpoint.
How does AnomalyArmor discover assets?
Assets are discovered automatically when you connect a source (Snowflake, BigQuery, Postgres, etc.) via the dashboard. The Assets API is read-only; it returns whatever the platform has discovered so far. If an expected table is missing, trigger a re-scan from the source’s page in the dashboard.
Does listing assets return column-level details?
No. GET /api/v1/assets returns metadata and row/column counts. To get the column schema (names, types, nullability, primary keys), call GET /api/v1/assets/{id} for a single asset. That keeps list responses small and fast when you have hundreds of tables.