> ## Documentation Index
> Fetch the complete documentation index at: https://docs.poixe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete All Stored Responses

<RequestExample>
  ```bash curl theme={"theme":{"light":"min-light","dark":"min-dark"}}
  # Dry run (recommended)
  curl -X DELETE "https://api.poixe.com/v1/recoveries?all=true&dry_run=true" \
    -H "Authorization: Bearer $POIXE_API_KEY" \
    -H "Content-Type: application/json"

  # Real delete
  curl -X DELETE "https://api.poixe.com/v1/recoveries?all=true" \
    -H "Authorization: Bearer $POIXE_API_KEY" \
    -H "Content-Type: application/json"
  ```
</RequestExample>

<ResponseExample>
  ```json real delete theme={"theme":{"light":"min-light","dark":"min-dark"}}
  {
    "deleted": 2,
    "message": "All recovery records deleted successfully.",
    "reason": "OK"
  }
  ```

  ```json dry run delete theme={"theme":{"light":"min-light","dark":"min-dark"}}
  {
    "deleted": 0,
    "would_delete": 2,
    "message": "Dry run only. No records deleted.",
    "reason": "DRY_RUN"
  }
  ```
</ResponseExample>

<div className="inline-flex flex-wrap items-center gap-4 rounded-lg border px-3 py-2">
  <Badge color="gray">DELETE</Badge>
  `https://api.poixe.com/v1/recoveries?all=true`
</div>

Deletes all stored records for the current user. This is a destructive operation, and you must explicitly include `all=true` as a confirmation parameter (to prevent accidental deletion).

You can also run a preview first with `dry_run=true`: it returns only the number of records expected to be deleted and does not actually delete anything.

## Authentication and request headers

Every API request must include your API key in the HTTP headers.

<ParamField header="Authorization" type="string" required>
  Bearer token. The format is `Bearer YOUR_API_KEY`.
</ParamField>

<ParamField header="Content-Type" type="string" required>
  Must be set to `application/json`.
</ParamField>

## Query parameters

<ParamField query="all" type="string" required>
  Must be `true`. Confirms that you want to "delete all".
</ParamField>

<ParamField query="dry_run" type="string">
  Optional: when `true`, only previews and does not delete; the response returns `would_delete`.
</ParamField>

## Response structure

<ResponseField name="deleted" type="integer">
  The number of records actually deleted (usually 0 for a dry\_run).
</ResponseField>

<ResponseField name="would_delete" type="integer">
  Returned only for a dry\_run: the number of records that would be deleted.
</ResponseField>

<ResponseField name="message" type="string">
  Result description.
</ResponseField>

<ResponseField name="reason" type="string">
  Result reason (such as `OK` / `DRY_RUN` / `CONFIRMATION_REQUIRED`).
</ResponseField>

<Callout type="warning" icon="info-circle">
  We recommend first calling `DELETE /v1/recoveries?all=true&dry_run=true` to confirm the count, and then performing the actual deletion:
  `DELETE /v1/recoveries?all=true`.
</Callout>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.