Purge a trace's content

DELETE 
/v1/projects/:project_id/traces/:trace_id/content

Deletes the trace's step payload and clears its content columns, cascading to every descendant trace in its execution tree and to their generations. The rows survive as auditable skeletons — ids, timestamps and step counts are preserved — with content_redacted_at set as verifiable proof the content is gone; a purged trace still reads back with GET /v1/projects/{project_id}/traces/{trace_id} (a 404 there would prove nothing about what was erased). Idempotent: purging an already-purged trace succeeds and leaves the original content_redacted_at in place.

Request

Responses

200

The purged trace skeleton.

401

Missing or invalid credentials.

404

The resource does not exist (existence is not leaked).

502

The upstream runtime could not complete the operation.