POST a dbt manifest as a partial or complete declared-lineage acquisition.
POST /v1/pipelines/dbt/manifest| Body field | Required | Description |
|---|---|---|
workspace_id | Yes | Target workspace. |
connector_id | Yes | Connector scope for relation resolution. |
manifest | Yes | Parsed dbt manifest object. |
project_id | No | Linked dbt project ID. |
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/dbt/manifest \
--header "Authorization: Bearer $EMBRASURE_API_TOKEN" \
--header "Content-Type: application/json" \
--header "Idempotency-Key: dbt-build-842" \
--data-binary @embrasure-dbt-manifest.jsonThe route returns 202. A complete acquisition needs an exact connector and project scope and a caller-supplied idempotency key. If the header and source_event_key are both present, they must match.
See pipelines and applications for a jq wrapper example and CI guidance.