Use Case: Create a 1 hr Open Play

This guide walks you through creating a 1-hour open play event for a specific pod and court, using sessions and bookings.

Content

In this use case, you will:

1. Select an area
2. Select a pod
3. Select a court (table)
4. Retrieve available sessions in a 1-hour time window
5. Create a booking (event)
6. Verify the event was created successfully

By the end of this guide, you will have a published 1-hour open play event assigned to a specific court.

Key Concepts

Before starting, understand these relationships:

1. Area → physical location grouping
2. Pod → group of courts inside an area
3. Table (Court) → individual playable surface
4. Session → bookable 30-minute time slot
5. SessionTable → a specific court within a specific session

Relationship hierarchy:

Area
 └── Pod
      └── Table (Court)

Pod
 └── Sessions (time-based)
      └── availableTables (SessionTable IDs)

Important: 1 Hour = 2 Sessions

Each session last 30 minutes.

To create a 1-hour event, you must book 2 consecutive 30-minute sessions

Flow Overview

Step	Purpose
1	Get areas, pods and courts
2	Get sessions inside time window
3	Create booking
4	Verify event

Outcome of This Section

You now understand:

• The system structure (area → pod → table)
• How sessions relate to pods
• Why sessionTable IDs are required for booking

In the next section, you will retrieve the list of areas, pods and courts to allow the user to choose where the event will take place.