Step 4 — Verify the Event

Confirm that the Open Play event exists and is correctly scheduled.

Starting Point

ou have successfully created and published an Open Play event for:

• March 4th
• 17:00 → 18:00 UTC
• Court 1 (C1)
• Status: PUBLISHED

The event is visible in the Admin dashboard.

Now we will confirm it using the API.

Retrieve Events

To verify the event, call the /events endpoint using the same time window used for booking.

curl -sS -X GET \
  -H "x-api-key: <your_api_key>" \
  "https://sandbox1.podplay.app/apis/v2/events?startTime=2026-03-04T17:00:00.000Z&endTime=2026-03-04T18:00:00.000Z"

Example Response (Trimmed)

{
  "items": [
    {
      "id": "ac8805ce-81af-4d34-b601-f9a977e7e14e",
      "type": "EVENT",
      "subtype": "OPEN_PLAY",
      "name": "Open Play Session",
      "startTime": "2026-03-04T17:00:00.000Z",
      "endTime": "2026-03-04T18:00:00.000Z",
      "status": "PUBLISHED",
      "admission": "OPEN",
      "bookingMode": "FREE_OF_CHARGE",
      "pods": {
        "items": [
          {
            "id": "b066d668-e64f-480a-ad31-110b3433c080",
            "displayName": "Pod 1"
          }
        ]
      },
      "tables": {
        "items": [
          {
            "table": {
              "id": "61e3f1c2-d23b-4eb3-bebb-77c4eeda6d03",
              "displayName": "Court 1",
              "displayNameShort": "C1"
            },
            "startTime": "2026-03-04T17:00:00.000Z",
            "endTime": "2026-03-04T18:00:00.000Z"
          }
        ]
      }
    }
  ]
}

What to Check in the Response

Inside items[], verify:

• Event name → "Open Play Session"
• startTime → 2026-03-04T17:00:00.000Z
• endTime → 2026-03-04T18:00:00.000Z
• Associated pod
• Associated table (Court 1 / C1)
• eventStatus → "PUBLISHED"

If the event appears with the correct:

• Time window
• Court
• Status

then the booking was successfully created and persisted.

Why This Step Matters

Even if the Admin UI shows the event, verifying via API confirms that:

• The booking was correctly stored
• The sessions were correctly linked
• The event is retrievable by other systems
• Your integration flow is complete

Final Outcome

You have successfully:

1. Retrieved the structure (areas → pods → courts)
2. Selected available sessions
3. Created a 1-hour Open Play booking
4. Verified the event via API

You now understand the complete booking flow for Open Play events — from structure discovery to published event verification.