Get schema changes
API Reference
Get Schema Changes
Retrieve recent schema changes detected for an asset
GET
Get schema changes
Get the history of schema changes for an asset. Use this to track drift, understand what changed, and build change management workflows.
When to Use
- Change tracking: Monitor schema drift over time
- Impact analysis: Understand what changed before troubleshooting
- Compliance: Audit schema modifications
- Integration: Sync changes to external systems
SDK & CLI Examples
Parameters
| Parameter | Type | Description |
|---|---|---|
asset_id | string | Asset ID or qualified name |
days_back | integer | Look back this many days (default: 30) |
change_type | string | Filter by type (see Change Types below) |
limit | integer | Max results (default: 100) |
Response
Response Fields
| Field | Description |
|---|---|
id | Unique change identifier |
change_type | Type of change (see Change Types) |
object_name | Name of changed column or table |
object_type | column or table |
old_value | Previous state (null for additions) |
new_value | New state (null for removals) |
detected_at | When the change was discovered |
discovery_id | Discovery run that found this change |
Change Types
| Type | Description | Impact |
|---|---|---|
column_added | New column appeared | Low - usually safe |
column_removed | Column no longer exists | High - breaks queries |
column_type_changed | Data type modified | Medium - may affect logic |
column_renamed | Detected as remove + add | High - breaks queries |
table_added | New table discovered | Low - informational |
table_removed | Table no longer exists | High - breaks queries |
constraint_changed | PK, FK, or unique modified | Medium - may affect joins |
Error Responses
| Status | Meaning |
|---|---|
401 | Invalid or missing API key |
404 | Asset not found |
429 | Rate limit exceeded |
Headers
Path Parameters
Query Parameters
Days to look back for changes
Required range:
1 <= x <= 365