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

Networking timeslots

Networking timeslots: available fields, filters, associations, and API operations.

Release timing: This page includes changes planned for 9 October 2026. See the deployment note before using the updated operations or inputs.

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/networking-timeslots

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/networking-timeslots' \
  --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": "networking-timeslot"
    }
  ],
  "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/networking-timeslots/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/networking-timeslots/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": "networking-timeslot"
  }
}

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/networking-timeslots

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/networking-timeslots' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "track_id": 502,
  "networking_area_id": 91,
  "start_time": "2026-09-03T10:15:00Z",
  "duration": 30
}'

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

View response structure
{
  "data": {
    "id": "1201",
    "type": "networking-timeslot"
  }
}

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/networking-timeslots/5601

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/networking-timeslots/5601' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "start_time": "2026-09-03T10:30:00Z",
  "duration": 45,
  "color": "#3478F6"
}'

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

View response structure
{
  "data": {
    "id": "1201",
    "type": "networking-timeslot"
  }
}

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/networking-timeslots/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/networking-timeslots/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.

registrant_list_ids and rating_registrant_list_ids are not supported write inputs for networking timeslots. They are ignored by Core input selection and do not configure networking or rating access. Use the supported inputs below; existing event access settings are managed separately.

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

Fields, filters and associations

Browse 25 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
track-id
Scope field: track_id
networking-area-id
Scope field: networking_area_id
parent-timeslot-id
Scope field: parent_timeslot_id
start-time
Scope field: start_time
end-time
Scope field: end_time
duration
Scope field: duration
color
Scope field: color
created-at
Scope field: created_at
updated-at
Scope field: updated_at
overflow-location-ids
Scope field: overflow_location_ids
meeting-points-total-count
Scope field: meeting_points_total_count
meeting-points-used-count
Scope field: meeting_points_used_count
meeting-points-free-count
Scope field: meeting_points_free_count
meetings-pending-count
Scope field: meetings_pending_count
meetings-accepted-count
Scope field: meetings_accepted_count
meetings-rejected-count
Scope field: meetings_rejected_count
meetings-cancelled-count
Scope field: meetings_cancelled_count
meetings-rescheduled-count
Scope field: meetings_rescheduled_count
meetings-chat-requested-count
Scope field: meetings_chat_requested_count
meetings-chat-replied-count
Scope field: meetings_chat_replied_count
meetings-draft-count
Scope field: meetings_draft_count
meetings-total-count
Scope field: meetings_total_count
meetings-chat-requests-count
Scope field: meetings_chat_requests_count
blocked-registrants-count
Scope field: blocked_registrants_count
  • Filters: networking_area_id, track_id, start_from, start_to, end_from, end_to.
  • Associations:
    • networking_area → response networking-area: name, meeting-type, uses-meeting-points, meeting-point-count, meeting-point-name, allow-overbooking, uses-meeting-capacity, meeting-capacity, default, requires-full-gating;
    • tables → response meeting-points: index, meeting-id, status (used or free).
GET .../networking-timeslots?start_from=2026-09-03T08:00:00Z&include=networking-area,meeting-points

Writing this resource

Writable fields: track_id, networking_area_id, parent_timeslot_id, start_time, end_time, duration, color.

Additional inputs: child_timeslot_ids (array).

{
  "track_id": 502,
  "networking_area_id": 91,
  "start_time": "2026-09-03T10:15:00Z",
  "duration": 30
}

The track must be a networking track. The networking area and referenced child sessions must belong to the event. These records are always created as reservable networking timeslots. Use start_time plus duration for scheduling: the declared end_time input is discarded by the downstream allowlist.

Last updated on October 9, 2026