POST a DataHub export into the same evidence and projection path as other lineage providers.
POST /v1/pipelines/lineage/datahub| Body field | Required | Description |
|---|---|---|
workspace_id | Yes | Target workspace. |
connector_id | Yes | Connector scope for imported assets. |
export | Yes | DataHub export object or array. |
import_source | No | Stable source label, up to 300 characters. |
completeness | No | partial or complete; default partial. |
source_event_key | No | Body alternative to Idempotency-Key. |
curl --request POST https://api.embrasure.ai/v1/pipelines/lineage/datahub \
--header "Authorization: Bearer $EMBRASURE_API_TOKEN" \
--header "Content-Type: application/json" \
--header "Idempotency-Key: datahub-export-2026-08-04" \
--data-binary @datahub-lineage-request.jsonThe route returns 202. Complete snapshots require exact connector and import-source scope and a new key for each acquisition. See ingest lineage.