Skip to main content
DELETE
/
events
/
{eventId}
/
attendees
/
{attendeeId}
curl -X DELETE -H "X-API-KEY: your_api_key" \
  https://www.gomry.com/api/v1/events/AbCdEfGhIjKlMnOpQrSt/attendees/tkt_AAA

​
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

​
eventId
string
required
The unique identifier of the event.
​
attendeeId
string
required
The unique identifier of the attendee (ticket).

​
Response

Returns 200 OK with: 
{ "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.
curl -X DELETE -H "X-API-KEY: your_api_key" \
  https://www.gomry.com/api/v1/events/AbCdEfGhIjKlMnOpQrSt/attendees/tkt_AAA