---
title: "Networking timeslots"
description: "Networking timeslots: available fields, filters, associations, and API operations."
lastModified: "2026-08-21"
---

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

**GET**

- Fields: `event-id`, `track-id`, `networking-area-id`, `parent-timeslot-id`, `start-time`, `end-time`, `duration`, `color`, `created-at`, `updated-at`, `overflow-location-ids`, `meeting-points-total-count`, `meeting-points-used-count`, `meeting-points-free-count`, `meetings-pending-count`, `meetings-accepted-count`, `meetings-rejected-count`, `meetings-cancelled-count`, `meetings-rescheduled-count`, `meetings-chat-requested-count`, `meetings-chat-replied-count`, `meetings-draft-count`, `meetings-total-count`, `meetings-chat-requests-count`, `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,tables
```

**POST/PATCH writable fields:** `track_id`, `networking_area_id`, `parent_timeslot_id`, `start_time`, `end_time`, `duration`, `color`.

**Additional inputs:** `registrant_list_ids`, `rating_registrant_list_ids`, `child_timeslot_ids`, all arrays.

```json
{
  "track_id": 502,
  "networking_area_id": 91,
  "start_time": "2026-09-03T10:15:00Z",
  "duration": 30,
  "registrant_list_ids": [401]
}
```

The track must be a networking track. The networking area and all referenced lists or child sessions must belong to the event. These records are always created as reservable networking timeslots.