Skip to content
Core API
Esc
↑↓navigate↵open⌘Jpreview
On this page

Meetings

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

Operations

Event-level resource. Every operation requires an enabled Core API scope for this resource and access to the URL context.

GETList records

/api/core/organizations/123/events/456/meetings

Permission: Read access. Readable fields, query filters and related objects must be selected in the scope.

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request GET \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/meetings' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}"

Response: 200 OK. A JSON:API data array and pagination metadata. Default page size 30; maximum 100.

View response structure
{
  "data": [
    {
      "id": "1201",
      "type": "meeting"
    }
  ],
  "meta": {
    "total_count": 1,
    "total_pages": 1,
    "current_page": 1
  }
}

Illustrative, with no additional response fields selected.

Errors: 400 for invalid parameter shapes; 403 for a missing/expired token or disallowed operation; 404 when the URL context, record or a referenced record is inaccessible; 429 for rate limits. Troubleshooting and retry guidance.

GETGet a record

/api/core/organizations/123/events/456/meetings/1201

Permission: Read access. Readable fields, query filters and related objects must be selected in the scope.

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request GET \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/meetings/1201' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}"

Response: 200 OK. A JSON:API data object; fields depend on the token scope.

View response structure
{
  "data": {
    "id": "1201",
    "type": "meeting"
  }
}

Illustrative, with no additional response fields selected.

Errors: 400 for invalid parameter shapes; 403 for a missing/expired token or disallowed operation; 404 when the URL context, record or a referenced record is inaccessible; 429 for rate limits. Troubleshooting and retry guidance.

POSTCreate a record

/api/core/organizations/123/events/456/meetings

Permission: Write access with the create action. Every request key must map to an allowed writable field; unconfigured inputs are ignored.

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request POST \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/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,
  "timeslot_id": 5501,
  "draft": true,
  "send_individual_notifications": false
}'

Response: 201 Created. Save data.id for later requests. Attributes come from Write-response fields.

View response structure
{
  "data": {
    "id": "1201",
    "type": "meeting"
  }
}

Illustrative, with no additional response fields selected.

Errors: 400 for invalid parameter shapes; 403 for a missing/expired token or disallowed operation; 404 when the URL context, record or a referenced record is inaccessible; 422 for validation or business rules; 429 for rate limits. Troubleshooting and retry guidance.

PATCHUpdate a record

/api/core/organizations/123/events/456/meetings/6001

Permission: Write access with the update action. Every request key must map to an allowed writable field; unconfigured inputs are ignored.

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request PATCH \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/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"
}'

Response: 200 OK. Attributes come from Write-response fields; these can differ from readable fields.

View response structure
{
  "data": {
    "id": "1201",
    "type": "meeting"
  }
}

Illustrative, with no additional response fields selected.

Errors: 400 for invalid parameter shapes; 403 for a missing/expired token or disallowed operation; 404 when the URL context, record or a referenced record is inaccessible; 422 for validation or business rules; 429 for rate limits. Troubleshooting and retry guidance.

PATCH changes supplied fields. Collection inputs can replace existing values; read the input notes before sending arrays.

DELETEDelete a record

/api/core/organizations/123/events/456/meetings/1201

Permission: Write access with the delete action.

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request DELETE \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/meetings/1201' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}"

Response: 204 No Content, with an empty response body.

Errors: 400 for invalid parameter shapes; 403 for a missing/expired token or disallowed operation; 404 when the URL context, record or a referenced record is inaccessible; 422 for validation or business rules; 429 for rate limits. Troubleshooting and retry guidance.

Deletion can remove related data or be refused by resource constraints. Read the resource notes and confirm the target before using this operation.

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

Fields, filters and associations

Browse 12 response fields

The scope chooses these response fields. id is always returned. Configuration names and response names can differ.

event-id
Scope field: event_id
timeslot-id
Scope field: timeslot_id
location-id
Scope field: location_id
current-status
Scope field: status
initial-status
Scope field: initial_status
admin-panel-created
Scope field: admin_panel_created
created-at
Scope field: created_at
updated-at
Scope field: updated_at
message
Scope field: message
requester-message
Scope field: requester_message
receiver-message
Scope field: receiver_message
is-group-meeting
Scope field: 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,meeting-point,status-history

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.

Last updated on August 21, 2026