asset

Get the workspace-wide asset <-> runnable graph

Changed on
get/w/{workspace}/assets/graph

Request

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

Path parameters

workspacestring required

Query parameters

asset_kindsstring

Filter by asset kinds (comma-separated list)

folderstring

Scope the graph to runnables in a single folder

dbt_script_hashstring

Render the dbt half of the graph as one version of a dbt script had it, rather than as the currently deployed one. Given this, folder no longer scopes the dbt nodes: the pinned version's own models and lineage are the answer, including models a later deploy removed.

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.

Changes