---
title: "Withdraw Event App Attendees Endpoint"
method: POST
path: "/internal/eventApp/withdrawAttendees"
---

# Withdraw Event App Attendees Endpoint

`POST /internal/eventApp/withdrawAttendees`

## Request

- Base URL: `https://api.pavoot.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.pavoot.com/internal/eventApp/withdrawAttendees`
- Auth: none declared

Remove people from Photos: person row, face template, gallery link.

Called when consent is withdrawn, or when an un-check-in has outlived its
grace window. This deletes biometric data on purpose and is not
recoverable — `delete_persons` also cascades `image_faces`, so every photo
already matched to them is unattributed too. That is the correct outcome
for a withdrawal and the reason Events debounces un-check-ins before
calling it.

## Request body

- WithdrawEventAttendeesRequest
  - `projectId` integer, required
  - `eventId` string, required
  - `contactIds` string[], required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-17** `b580245ec7c5`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/pavoot/apis/pavoot-api/changes/internal/eventApp/withdrawAttendees/post.md)

---

[API](https://skmtc.dev/pavoot/apis/pavoot-api.md) - [All operations](https://skmtc.dev/pavoot/apis/pavoot-api/llms.txt) - [OpenAPI document](https://skmtc.dev/pavoot/apis/pavoot-api/revisions/8c0cd91c2a05?raw)