---
title: "Delete response"
method: DELETE
path: "/responses/{response_id}"
tags: ["responses-api"]
---

# Delete response

`DELETE /responses/{response_id}`

Hard-deletes a response and every fusillade row that backs it (including the dedicated request_templates row carrying the prompt body). Provided for right-to-erasure compliance.

Token / cost analytics in `http_analytics` and billing transactions in `credits_transactions` are preserved — they are denormalized off the fusillade schema and survive the erasure.

## Path parameters

- `response_id` string, required

## Response `200`

Response deleted.

- ResponseDeleted — Response body for `DELETE /v1/responses/{response_id}`. Matches the OpenAI Responses API delete shape — clients (including the OpenAI SDK) parse this into a typed `ResponseDeleted`, so the field names and the literal `"object": "response"` discriminator are load-bearing.
  - `deleted` boolean, required
  - `id` string, required
  - `object` 'response', required — Always `"response"` for the deletion envelope.

## Other responses

- `401` — Invalid or missing API key. Ensure your `Authorization` header is set to `Bearer YOUR_API_KEY`.
- `404` — Response not found or you don't have access to it.
- `500` — An unexpected error occurred. Retry the request or contact support if the issue persists.

---

[API](https://skmtc.dev/doubleword/apis/doubleword-api.md) · [All operations](https://skmtc.dev/doubleword/apis/doubleword-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/doubleword/doubleword-api/revisions/6617202865d8/schema)