> ## 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 Attendee

> Soft-delete an attendee (ticket)

# Delete Attendee

Soft-deletes a single attendee (ticket). Routes through the same canonical action as `PATCH { status: "deleted" }`, so refund/`statusChangeHistory` side effects fire correctly.

Requires the `attendees:write` scope.

## Path Parameters

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

<ParamField path="attendeeId" type="string" required>
  The unique identifier of the attendee (ticket).
</ParamField>

## Response

Returns `200 OK` with:

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

## Errors

* `404 Attendee not found` — ticket missing or not owned by your org.
* `422` — the underlying delete was rejected (e.g. the ticket is part of an in-flight upgrade flow). The response `error` field carries the reason.

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

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