Skip to main content
 print this page

Delete the dataset

DELETE 
/datasets/:id

Deletes a dataset. The caller must be the dataset owner. Deletion behaviour depends on the dataset type and registration status

  • View datasets (DatasetType = view) — deletion is always asynchronous. A Lambda is invoked to drop the view and the response returns immediately with "Dataset deletion triggered."

  • Non-view datasets with RegistrationStatus = pending — deletion is synchronous. DynamoDB metadata and related artifacts are removed directly and the response returns "Dataset deletion successful".

  • Non-view datasets with RegistrationStatus = completed or delete-failed — deletion is asynchronous. A Step Function is triggered to clean up S3 files, Redshift/Glue tables, DynamoDB metadata, and other resources. The response returns immediately with "Dataset deletion triggered."

Force delete — applicable only to Redshift datasets. When a Redshift dataset's only dependencies are Redshift views, passing force_delete=true bypasses those view dependencies and proceeds with deletion. Using force_delete on a non-Redshift dataset returns an error.

Dependent resources — if the dataset has dependent resources (jobs, pipelines, views, datalabs, dashboards, etc.), the API returns HTTP 400 with a DependentResources array listing each dependency category and its entries. Resolve or remove these dependencies before retrying.

Request​

Responses​

Dataset deleted (sync) or deletion triggered (async). Check the Message field to determine which path was taken.

Response Headers
    Access-Control-Allow-Origin
    Access-Control-Allow-Methods
    Access-Control-Allow-Headers