Skip to content
campaiDeveloper
campai.com

Booking · Seat groups

POST/{organizationId}/booking/seatGroups/{seatGroupId}/update

Update seat group

Updates a seat group's name and maxAttendees using the organization and seat group IDs. The endpoint returns no response body.

Permissions

Send an API key of the organization in the path, using the X-API-Key header.

Who may call it

  • Callers must have organization access and the event.edit permission.

Request

Path parameters

  • organizationIdidrequired
  • seatGroupIdidrequired

Body

Content-Type: application/json

  • namestringrequired

    1–60 characters

  • maxAttendeesintegerrequired
Request
curl --fail-with-body --silent --show-error --max-time 30 --globoff \
  --request POST 'https://cloud.campai.com/api/YOUR_ORGANIZATION_ID/booking/seatGroups/YOUR_SEAT_GROUP_ID/update' \
  --header 'X-API-Key: YOUR_API_KEY'

No request that worked has been recorded yet, so the body is not shown.

Response

200 Successful response

No response body is specified.

What else happens

  • Updates name and maxAttendees on the matching eventSeatGroups record.
  • For each uncanceled future event using the seat group that has waitlisted attendees, starts a booking.offerManyAttendeeWaitlistSeats job on DefaultQueue.

Errors

Other errors

StatusErrorWhen
404The seat group was not foundIf the seat group is not found in the organization, the endpoint returns HTTP 404 with key routes.booking.seatGroups.noSeatGroup.

Errors nearly every request can meet are listed under Errors.