Get Document Lineage
Return a document's downstream footprint: the pipelines that consumed it, the data products built from them, the field-registry concepts it contributed, and the cases it belongs to.
Returns the document's lineage — its downstream footprint across the platform. This is the "used in" view: where a document ended up after ingestion, rather than what it contains. It answers questions like "which pipelines consumed this file?", "which data products ship its values?", and "which cases does it belong to?".
The response groups the footprint into sections: pipelines (the One Engine runs that included the document), data_products (datasets built from those pipelines), field_registry (the canonical concepts the document contributed, with per-tier counts and a sample), cases, and business_cases. Each entry carries a deep link to the corresponding public surface, so you can follow lineage outward without constructing URLs yourself.
/v1/documents/{id}/lineageResponse
Response fields
curl
Response
{
"document_id": "7f3a1b2c-0000-0000-0000-000000000000",
"pipelines": [
{ "id": "c3d4e5f6-...", "name": "Delivery Notes", "status": "completed",
"document_status": "completed", "schema_id": "b2c3d4e5-...",
"schema_name": "Delivery Note", "links": { "self": "/v1/pipelines/c3d4e5f6-..." } }
],
"data_products": [
{ "id": "d4e5f6a7-...", "name": "Q2 Deliveries", "status": "active",
"links": { "self": "/v1/data-products/d4e5f6a7-..." } }
],
"field_registry": {
"total": 18,
"by_tier": [ { "tier": 1, "count": 12 }, { "tier": 2, "count": 6 } ],
"sample": [ { "canonical_name": "invoice_total", "display_name": "Invoice Total", "tier": 1 } ],
"links": { "fields": "/v1/fields?document_id=7f3a1b2c-..." }
},
"cases": [],
"business_cases": []
}