Purge generation content
DELETE/v1/projects/:project_id/generations/:generation_id/content
Clears the generation's content — metadata, error, extraction, and the internal recovery state of a paused run — and stamps content_redacted_at.
The usage and audit skeleton is preserved: ids, timestamps, status, stop reason, and the attribution fields (action_id, trigger_id, orchestration_run_id, node_id, node_attempt, agent_version, routing) the billing ledger reads. A purged generation reads back as that skeleton, not a 404.
This does not delete the parent trace's steps object, which holds this generation's content alongside its siblings'. To erase the run's content completely, purge the trace (DELETE /v1/projects/{project_id}/traces/{trace_id}/content), which cascades here.
Idempotent — purging an already-purged generation succeeds and leaves the original content_redacted_at in place.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
- 502
- 4XX
The purged generation skeleton
The request was malformed or failed validation.
Unauthorized
Forbidden
Generation not found
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there