Get the entity relationship map for an asset

GET 
/catalog/:datasource_id/item-dependencies/:asset_id

Returns the dependency graph of a catalog asset: the asset itself plus the assets it depends on and that depend on it, as a flat node list with edges carried inside each node.

Important restriction: this operation is supported only for ArcGIS datasources. Calling it for a datasource of any other type is rejected with IPV-1002, regardless of whether the asset exists.

The caller needs at least read-only access on the datasource.

An asset with no dependencies is not an error: the response is HTTP 200 with a single-element graph describing the asset itself and empty Input and Output arrays.

Note this returns a different shape from GET /{resource}/{id}/lineageV2, which uses the OpenLineage-based LineageResponse schema.

Request

Responses

200

The dependency graph. Returned even when the asset has no dependencies, in which case the graph holds only the asset itself.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

400

Input validation or authorization failure. Body is {"Message": " - "}.

Note that IPV-1002 covers four distinct causes, distinguishable only by the message text: the datasource does not exist, the datasource is not an ArcGIS datasource, the asset does not exist within that datasource, and depth is out of range or not an integer. An invalid traversal_direction also uses IPV-1002. AUTH-1012 indicates the caller lacks read-only access on the datasource, and AUTH-1001 that the role_id header is missing.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

500

Backend failure. Body is {"Message": " - "}.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers