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

Virtual Sources

Create, update, and delete virtual sources and virtual objects programmatically via the Decube API.

The Virtual Sources API lets you manage virtual sources and their objects programmatically. Use these endpoints to bulk-create asset hierarchies, integrate virtual source management into your data pipelines, or automate the lifecycle of virtual assets.

All write operations require the admin_data_source:edit permission. Read operations require admin_data_source:view.

Virtual objects created via API follow the same Decube data model as those created in the UI. See Overview for an overview of supported object types.

Virtual Sources

Create a virtual source

Creates a new virtual source. The source name must be unique across all sources in your workspace.

Create Virtual Source

post

Creates a new virtual source using the provided request body.

Body
namestringRequired
Responses
200

Successful Response

application/json
source_idintegerRequired
post/virtual_sources

Update a virtual source

Updates the name or description of an existing virtual source.

Update Virtual Source

put

Updates an existing virtual source using the provided request body.

Body
source_idintegerRequired
namestringRequired
Responses
200

Successful Response

application/json
anyOptional
put/virtual_sources

No content

Delete a virtual source

Permanently deletes a virtual source and all virtual objects under it. This is irreversible.

Delete Virtual Source

delete

Deletes a virtual source by ID.

Query parameters
source_idintegerRequired
Responses
200

Successful Response

application/json
anyOptional
delete/virtual_sources

No content

Virtual Objects

All virtual object endpoints operate only on assets under a virtual source. Passing an identifier that resolves to a native source asset returns a 400.

Create a virtual object

Creates a virtual object under a virtual source. Pass a type field to specify the asset type — supported values are COLLECTION (Schema), DATASET (Table), PROPERTY (Column), DATA_JOB, DATA_TASK, DASHBOARD, and CHART. The asset type cannot be changed after creation.

Create Virtual Asset

post

Creates a new virtual asset using the provided request body.

Body
or
or
or
or
or
or
Responses
200

Successful Response

application/json
attrsany ofRequired
or
or
or
or
or
or
or
object · DataTaskAttributesOptional
or
or
or
or
post/virtual_assets

Update a virtual object

Updates one or more fields on an existing virtual object. Only fields included in the request are updated.

Patch Virtual Asset

patch

Updates (partially) an existing virtual asset using the provided request body.

Body
or
or
or
or
or
or
Responses
200

Successful Response

application/json
attrsany ofRequired
or
or
or
or
or
or
or
object · DataTaskAttributesOptional
or
or
or
or
patch/virtual_assets

Delete a virtual object

Soft-deletes a virtual object and all its children. Soft-deleted objects are removed from the Catalog, lineage, and search results but remain in the database until the parent virtual source is deleted.

Delete Virtual Asset

delete

Deletes a virtual asset by ID.

Query parameters
asset_idintegerRequired
asset_typestring · enumRequiredPossible values:
Responses
200

Successful Response

application/json
anyOptional
delete/virtual_assets

No content

Last updated