Meetings

Meetings: available fields, filters, associations, and API operations.

Path: events/{event_id}/meetings
Methods: GET collection/record, POST, PATCH, DELETE.

GET

• Fields: event-id, timeslot-id, location-id, current-status, initial-status, admin-panel-created, created-at, updated-at, message, requester-message, receiver-message, is-group-meeting.
• Filters: timeslot_id, admin_panel_created, status, registrant_id, networking_area_id, start_from, start_to, sponsor_id.
• Associations:
  • participants: registrant-id, role, status, created-at, updated-at;
  • timeslot: start-time, end-time, networking-area-id;
  • location: name;
  • table → response meeting-point: index;
  • status_changes → response status-history: state, timeslot-id, registrant-id, message, requester-message, receiver-message, created-at.
• Row restriction: named sponsor, limiting meetings to those involving representatives of selected sponsors.

GET .../meetings?status=accepted&start_from=2026-09-03T08:00:00Z&include=participants,timeslot,table,status_changes

POST requires requester_registrant_id and receiver_registrant_id. Other inputs are additional_registrant_ids (array), timeslot_id, location_id, message, requester_message, receiver_message, send_individual_notifications, draft, preferred_table_index.

{
  "requester_registrant_id": 1201,
  "receiver_registrant_id": 1202,
  "additional_registrant_ids": [1203],
  "timeslot_id": 5501,
  "location_id": 88,
  "message": "Let's discuss distribution",
  "send_individual_notifications": true,
  "draft": false,
  "preferred_table_index": 4
}

Meetings are accepted by default; draft: true creates a draft. All registrants, timeslots, and locations must be in the event. Under a sponsor row restriction, the requester must represent one of the restricted sponsors.

PATCH inputs: additional_registrant_ids, timeslot_id, location_id, message, requester_message, receiver_message, send_individual_notifications, status.

{
  "timeslot_id": 5502,
  "additional_registrant_ids": [1203, 1204]
}

additional_registrant_ids replaces the additional-participant configuration while preserving requester and receiver roles. The only exposed status transition is cancellation:

{
  "status": "cancelled",
  "message": "Cancelled by the event organizer"
}

DELETE hard-deletes the meeting and its dependent data.