Sign in

v106

OpenAPI 3.0.3Apache 2.0raw.githubusercontent.com2026-08-03812347972.4 KB
job

Get the asset graph as one run saw it

The workspace asset graph with its dbt half pinned to what a single run built. Only a dynamic descriptor (a {{ }} placeholder in vars) leaves a per-run snapshot; without one for this job the pinned version's own graph answers, so a run page may use this route unconditionally. Authorized through the job, the same gate as run_progress — pinning to a run is job-scoped, which is why assets/graph cannot do it.

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

Path parameters

workspacestring required
idstring uuid required

The job whose graph to render

Query parameters

asset_kindsstring

Filter by asset kinds (comma-separated list)

folderstring

Scope the graph to runnables in a single folder

dbt_script_hashstring

Fallback only, for a job that names no deployed script — a preview or a flow. For a script job the version comes from the job row itself, so this is ignored: which deploy's models, SQL and ref() lineage are shown is not the caller's to choose.

Response

asset graph nodes, lineage edges and trigger edges

dbt_snapshot_jobstring uuid

The job whose own snapshot the dbt half was resolved from, when one was asked for and found. A run page polls the graph while its job runs, because a dynamic descriptor's snapshot is written mid-run, and this is what tells it to stop. Omitted when the answer came from the version's deployed graph.

dbt_graph_ingested_atstring date-time

When the dbt half on screen was parsed, for a graph pinned to a job. What the dbt editor labels its provenance with — "parsed from the editor at 14:32" against "as of last deploy" — since the two are drawn identically and the ambiguity would otherwise just move into the editor. Omitted for the unpinned workspace graph, which spans every project and so has no one time.