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

# Delete Experience

> Soft-delete an experience

# Delete Experience

Soft-deletes an experience. The experience is hidden from the dashboard, its public page, and the [List Experiences](/api-reference/experiences/list-experiences) endpoint. The underlying record is kept, so the id stays reserved and historical reporting is unaffected.

Only experiences owned by your organization can be deleted; any other experience returns `404`.

Deleting does **not** cancel or refund the experience's sessions and bookings, and attendees are **not** notified — handle those from the dashboard first if needed.

An experience that is already deleted is no longer visible to your key and returns `404`.

Requires the `experiences:write` scope.

## Path Parameters

<ParamField path="experienceId" type="string" required>
  The unique identifier of the experience.
</ParamField>

## Response

Returns `200 OK` with:

```json theme={null}
{ "deleted": true, "id": "AbCdEfGhIjKlMnOpQrSt" }
```

## Errors

* `404 Experience not found` — the experience does not exist, is already deleted, or is not owned by your organization.
* `403 insufficient_scope` — the API key does not have `experiences:write`.

<RequestExample>
  ```bash cURL theme={null}
  curl -X DELETE -H "X-API-KEY: your_api_key" \
    https://www.gomry.com/api/v1/experiences/AbCdEfGhIjKlMnOpQrSt
  ```

  ```javascript JavaScript theme={null}
  await fetch("https://www.gomry.com/api/v1/experiences/AbCdEfGhIjKlMnOpQrSt", {
    method: "DELETE",
    headers: { "X-API-KEY": "your_api_key" },
  });
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={null}
  { "deleted": true, "id": "AbCdEfGhIjKlMnOpQrSt" }
  ```

  ```json 404 Not Found theme={null}
  { "error": "Experience not found" }
  ```
</ResponseExample>