Endpoints
Get Schema Summary
Response
List Schema Changes
Query Parameters
Response
Trigger Schema Check
Requires
read-write or admin scope.Query Parameters
Response
Change Types
Use Case: Post-Deploy Schema Check
Trigger a schema check after deploying dbt models:Common Questions
How does AnomalyArmor detect schema changes?
A baseline schema snapshot is taken the first time an asset is profiled. On every scan (scheduled or triggered viaPOST /schema/{id}/refresh), the current column list, types, and nullability are diffed against the baseline and any delta is written to the changes feed. The previous_schema_hash and current_schema_hash fields let you correlate changes across runs.
Can I trigger a schema check on demand after a dbt deploy?
Yes. CallPOST /api/v1/sdk/schema/{id}/refresh?wait=true (or client.schema.refresh(asset, wait=True)) in your post-deploy step. The synchronous response includes changes_detected and the change list, so you can fail the deploy pipeline if a breaking change lands unexpectedly.
Which change types are reported?
The feed reportscolumn_added, column_removed, column_type_changed, column_renamed, table_created, and table_dropped. Renames are heuristic and are sometimes reported as paired add/remove when the column’s data distribution has also shifted.