---
title: "Bulk Attendee Card Flags"
method: PATCH
path: "/events/{event_id}/tito-attendees/bulk-card"
tags: ["tito"]
---

# Bulk Attendee Card Flags

`PATCH /events/{event_id}/tito-attendees/bulk-card`

## Request

- Base URL: `https://api.confbuilder.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.confbuilder.com/events/{event_id}/tito-attendees/bulk-card`
- Auth: none declared

Organizer wall-publish flags for MANY attendees in one request — the
bulk approve/publish/unapprove flows used to fire one PATCH per ticket ref
(each with its own auth resolution + commit).

Same approve-before-publish rule as the single endpoint, but batch-shaped:
publishing (embedEnabled=true) only lands on rows already card-approved
(or approved by the same request) — everything else is returned in
`skipped` instead of erroring.

## Path parameters

- `event_id` string, required

## Request body

- AttendeeBulkCardFlagsUpdate: Batch of update_attendee_card_flags — one HTTP for the bulk approve/ publish/unpublish flows instead of one PATCH per ticket ref.
  - `refs` string[], required
  - `cardApproved` boolean, nullable
  - `embedEnabled` boolean, nullable
  - `promoCardApproved` boolean, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/confbuilder/apis/confbuilder-api.md) · [All operations](https://skmtc.dev/confbuilder/apis/confbuilder-api/llms.txt) · [OpenAPI document](https://skmtc.dev/confbuilder/apis/confbuilder-api/revisions/9e576d664e16?raw)