Skip to main content
POST
cURL
Deletes several transformations in one call. The request body takes a list of pipeline slugs, not transformation IDs.
Queries, Notebooks, and Histories are all served by the transformations endpoints, so a single request may mix all three. They differ only by type: sql for a Query, python or pyspark for a Notebook, and scd_type_2 for a History.
This endpoint uses POST rather than DELETE because OpenAPI does not document a request body on DELETE. It deletes — it does not create anything.

Request body

Response

Returns 200 OK with a summary of what the action did, rather than the deleted objects.
The operation is all-or-nothing: nothing is deleted unless every listed transformation passes the same checks a single Delete Transformation call would apply. There is no undelete endpoint, so deletion cannot be reversed through the Platform API.

Example

Python example: delete every transformation carrying a given tag

Authentication

This endpoint requires an API key in the x-api-key header. MCP tokens cannot delete resources and are rejected with 403 Forbidden.

Authorizations

x-api-key
string
header
required

API Key authentication. Format: 'x-api-key: api_key'

Body

transformations
string[]

Slugs of the transformations to act on.

Response

200 - application/json

The summary a bulk action returns instead of the affected objects.

message
string
required

Human-readable summary of what the bulk action did.