---
title: "Sync Event App Attendees Endpoint"
method: POST
path: "/internal/eventApp/syncAttendees"
---

# Sync Event App Attendees Endpoint

`POST /internal/eventApp/syncAttendees`

## 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/syncAttendees`
- Auth: none declared

Import checked-in, consented attendees pushed by Events.

Returns a per-contact outcome, which is the point: Events gates on "has an
avatar URL", but whether that image contains a face Rekognition can index
is decided HERE. Without reporting it back, a guest whose photo has no
detectable face would sit in Events as successfully imported and never
appear in a gallery, with nothing anywhere saying why.

## Request body

- SyncEventAttendeesRequest
  - `projectId` integer, required
  - `eventId` string, required
  - `eventName` string, nullable
  - `attendees` object[]
  - `consentMode` string
  - `consentSlug` string, nullable
  - `consentValue` string, nullable
  - `ackBy` string, nullable
  - `ackEmail` string, nullable
  - `ackName` string, nullable
  - `ackAt` string, nullable
  - `ackVersion` string, nullable
  - `ackText` string, nullable
  - `ackIp` string, nullable

## 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/syncAttendees/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)