Read lineage impact

GET upstream and downstream impact with optional multi-column what-if analysis.

GET /v1/lineage/impact

ParameterRequiredConstraints
workspace_idYesNon-empty string.
connector_idYesConnector containing the root table.
relation_refYesResolvable table reference.
column_refNoRepeat for multiple columns.
directionNoupstream, downstream, or both; default both.
max_depthNo1 to 10.
max_nodesNo1 to 500.
curl --get https://api.embrasure.ai/v1/lineage/impact \
  --header "Authorization: Bearer $EMBRASURE_API_TOKEN" \
  --data-urlencode "workspace_id=workspace-1" \
  --data-urlencode "connector_id=connector-1" \
  --data-urlencode "relation_ref=project.dataset.orders" \
  --data-urlencode "column_ref=customer_id" \
  --data-urlencode "direction=downstream"
{
  "workspace_id": "workspace-1",
  "connector_id": "connector-1",
  "graph_found": true,
  "has_lineage": true,
  "root": {"relation_ref": "project.dataset.orders"},
  "upstream": [],
  "downstream": [{"relation_ref": "project.marts.customer_rollup"}],
  "edges": [],
  "truncated": {},
  "limits": {"max_depth": 5, "max_nodes": 200},
  "blast_radius": {},
  "precision": {"requested": "column"},
  "column_lineage": {},
  "lineage_resolution": {"method": "live_walk", "fallback_reason": "no_ready_generation"},
  "as_of": "2026-08-04T20:15:00+00:00"
}

Inspect truncated and precision before treating absence as complete. See column lineage.