For the complete documentation index, see llms.txt. This page is also available as Markdown.

Lineage

The dependencies between resources. Learn more about lineage here.

List Lineage

get
/api/v1/lineage/manual/

Get lineage objects with optional filtering by source and destination entity.

Authorizations
Query parameters
from_entitystring · nullableOptional
from_entity_idstring · nullableOptional
from_entity__instring · nullableOptional
to_entitystring · nullableOptional
to_entity_idstring · nullableOptional
to_entity__instring · nullableOptional
integration_typestring · nullableOptional
integration__typestring · nullableOptional
pageintegerOptionalDefault: 1
Responses
200

OK

application/json
countintegerRequired
total_pagesintegerRequired
get/api/v1/lineage/manual/
200

OK

Create new Lineage

post
/api/v1/lineage/manual/

Create a new lineage object manually. Only one direction of the relationship needs to be created. The opposite direction of the lineage is automatically generated.

Authorizations
Body
from_entitystringRequired
to_entitystringRequired
directionstring · enumOptionalPossible values:
Responses
200

OK

application/json
idstring · uuidOptional
created_atstring · date-timeRequired
updated_atstring · date-timeRequired
from_entity_idstring · uuidRequired
to_entity_idstring · uuidRequired
directionstring · nullableOptional
workspace_idstring · uuidRequired
is_manualbooleanOptionalDefault: false
post/api/v1/lineage/manual/

Get Lineage

get
/api/v1/lineage/manual/{lineage_id}/

Get a lineage object by its ID.

Authorizations
Path parameters
lineage_idstringRequired
Responses
200

OK

application/json
idstring · uuidOptional
created_atstring · date-timeRequired
updated_atstring · date-timeRequired
from_entity_idstring · uuidRequired
to_entity_idstring · uuidRequired
directionstring · nullableOptional
workspace_idstring · uuidRequired
is_manualbooleanOptionalDefault: false
get/api/v1/lineage/manual/{lineage_id}/
200

OK

Delete Lineage

delete
/api/v1/lineage/manual/{lineage_id}/

Delete a lineage object by its ID.

Authorizations
Path parameters
lineage_idstringRequired
Responses
204

No Content

No content

delete/api/v1/lineage/manual/{lineage_id}/
204

No Content

No content

Preview Lineage from Query

get
/api/v1/lineage/lineage_from_query/

Preview Lineage from a Query.

Authorizations
Query parameters
sqlstringRequired

The SQL query to analyze for lineage relationships

Example: SELECT a.customer_id, b.order_id FROM customers a JOIN orders b ON a.customer_id = b.customer_id
dialectstringRequired

SQL dialect of the query (e.g. postgresql, bigquery)

Example: postgresql
table_idstringOptional

ID of target table (optional)

Example: 550e8400-e29b-41d4-a716-446655440000
default_databasestringOptional

Default database name for resolving table references (optional)

Example: production
default_schemastringOptional

Default schema name for resolving table references (optional)

Example: public
Responses
200

OK

application/json
sqlstringRequired
get/api/v1/lineage/lineage_from_query/
200

OK

Create Lineage from Query

post
/api/v1/lineage/lineage_from_query/

Create Lineage from a Query.

Authorizations
Body
sqlstringRequired
dialectstringRequired
table_idstring · nullableOptional
default_databasestring · nullableOptional
default_schemastring · nullableOptional
Responses
200

OK

No content

post/api/v1/lineage/lineage_from_query/

No content

Create Lineage from Query and Removes Existing Upstream Non-Manual Lineage from Target Table

patch
/api/v1/lineage/lineage_from_query/

Create Lineage from Query and Removes Existing Upstream Non-Manual Lineage from Target Table.

Authorizations
Body
sqlstringRequired
dialectstringRequired
table_idstring · nullableOptional
default_databasestring · nullableOptional
default_schemastring · nullableOptional
Responses
200

OK

No content

patch/api/v1/lineage/lineage_from_query/

No content

Create new Lineage

post
/api/v1/lineage/

Create a new lineage object manually. Only one direction of the relationship needs to be created. The opposite direction of the lineage is automatically generated.

Authorizations
Body
from_entitystringRequired
to_entitystringRequired
directionstring · enumOptionalPossible values:
Responses
200

OK

application/json
idstring · uuidOptional
created_atstring · date-timeRequired
updated_atstring · date-timeRequired
from_entity_idstring · uuidRequired
to_entity_idstring · uuidRequired
directionstring · nullableOptional
workspace_idstring · uuidRequired
is_manualbooleanOptionalDefault: false
post/api/v1/lineage/

Last updated

Was this helpful?