Sign in
job

Get relations' project column lineage as one run saw it

Changed on

The same answer as assets/column_lineage, for the project version a single job ran — including the dbt editor's parse of its own buffer, whose graph belongs to that job and is reachable no other way. One project answers here, the one the run is of, since the graph this annotates is that project's too. Authorized through the job, the same gate as dbt_graph. Reaching the run is not on its own enough to read the project: a caller with no access to the script gets its relations and ref() edges from dbt_graph and an empty answer here, exactly as that endpoint redacts the model's SQL.

get/w/{workspace}/jobs/dbt_column_lineage/{id}

Request

  • Base URL: /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/w/{workspace}/jobs/dbt_column_lineage/{id}
  • Auth: one of:
    • HTTP bearer
    • API key in cookie token

Path parameters

workspacestring required
idstring uuid required

The job whose graph the lineage is read from

Query parameters

asset_pathstring[] required

The dbt:// relations whose lineage to return. Repeated, once per relation, and answered as one union. At least one, and at most 1000 — a request naming none, or more than that, is refused rather than answered with an empty component.

Response

the relations' column-level lineage

truncatedboolean required

The component reaches further than edges, which holds the part nearest the asked-for relations. A trace that stops short is otherwise indistinguishable from one that ends.

Changes