Responses API
Delete Response
Delete a response by ID.
DELETE
Headers
Path Parameters
Deleting one turn keeps the rest of the thread
A stored turn can be the middle of a conversation, with turns chained after it. Deleting it re-links its children onto its own parent, so the thread closes over the gap and the turns older than the deleted one stay reachable from the newer ones. Without that, forgetting a single turn would silently take every turn before it out of the next continuation’s history — the client asked to delete one response, not the conversation. Deleting the newest turn is simply a delete (it has no children), and deleting the oldest correctly leaves its child at the head of the thread.The same applies to a turn dropped by
store: false:
the eviction re-links the thread exactly as an explicit delete does.Supported Providers
DELETE /v1/responses/{id} is provider-agnostic — it applies to any response Bud stored,
whichever model produced it. Deleting a response the calling API key does not own returns
404.