Meetings

Create and update meetings with complete curl request examples.

Collection path: events/{event_id}/meetings

Input	Type	POST	PATCH	Notes
`requester_registrant_id`	Scalar ID	Required	Ignored	Requester must belong to the event. Under a sponsor restriction, the requester must represent an allowed sponsor.
`receiver_registrant_id`	Scalar ID	Required	Ignored	Receiver must belong to the event.
`additional_registrant_ids`	Array of scalar IDs	Optional	Optional	Additional participants. PATCH fully reconfigures only the additional participants, preserving requester and receiver.
`timeslot_id`	Scalar ID	Required for the scheduled meeting create path	Optional for draft meetings	PATCH can move a draft meeting; accepted meetings are not rescheduled by this mutation.
`location_id`	Scalar ID or `null`	Optional	Optional	Must belong to the event. `null` clears the location. Changing it frees the assigned meeting point.
`message`	Scalar string or `null`	Optional	Optional	Creation/status message; also used as the cancellation message.
`requester_message`	Scalar string or `null`	Optional	Optional	Participant-specific message.
`receiver_message`	Scalar string or `null`	Optional	Optional	Participant-specific message.
`send_individual_notifications`	JSON boolean	Optional	Ignored	On POST, notifications are sent only when true.
`draft`	JSON boolean	Optional	Ignored	On POST, true creates a draft; otherwise the meeting is accepted.
`status`	Scalar string	Ignored	`cancelled` only	Other supplied values do not expose another transition.
`preferred_table_index`	Scalar number or `null`	Optional	Optional for draft meetings	Selects or changes a reserved meeting point when available.

POST a meeting

curl --request POST \
  --url "${BRELLA_API_BASE_URL}/api/core/organizations/${BRELLA_ORGANIZATION_ID}/events/${BRELLA_EVENT_ID}/meetings" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "requester_registrant_id": 1201,
    "receiver_registrant_id": 1202,
    "additional_registrant_ids": [1203],
    "timeslot_id": 5501,
    "location_id": 88,
    "message": "Let us discuss distribution",
    "requester_message": "I would like to discuss the Nordic market",
    "receiver_message": "Please bring your channel overview",
    "send_individual_notifications": true,
    "draft": false,
    "preferred_table_index": 4
  }'

The response type is meeting. Useful write-response fields include timeslot_id, location_id, status (returned as current-status), message, admin_panel_created, and updated_at.

PATCH a meeting

This example changes a draft meeting’s timeslot and preferred point and replaces its additional participants.

curl --request PATCH \
  --url "${BRELLA_API_BASE_URL}/api/core/organizations/${BRELLA_ORGANIZATION_ID}/events/${BRELLA_EVENT_ID}/meetings/6001" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "timeslot_id": 5502,
    "preferred_table_index": 6,
    "additional_registrant_ids": [1203, 1204],
    "message": "Moved to the later slot"
  }'

Cancellation is a separate PATCH shape:

curl --request PATCH \
  --url "${BRELLA_API_BASE_URL}/api/core/organizations/${BRELLA_ORGANIZATION_ID}/events/${BRELLA_EVENT_ID}/meetings/6001" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "status": "cancelled",
    "message": "Cancelled by the event organizer"
  }'

When status is cancelled, the cancellation branch handles the request; sibling scheduling and participant changes should be sent in a separate request before cancellation if needed.