> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daily.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Meetings

> Using our REST API, the /meetings endpoint lets a developer get a list of meeting sessions.

## The "meeting" object

```json theme={null}
{
  "id": "82b92a0b-52cf-4495-f1bf-4d58a98a99b7",
  "room": "room-3",
  "start_time": 1549391714,
  "duration": 1650,
  "ongoing": true,
  "max_participants": 2,
  "participants": [
    {
      "user_id": null,
      "user_name": null,
      "participant_id": "11111111-2222-3333-4444-555555555555",
      "join_time": 1549391690,
      "duration": 1626
    },
    {
      "user_id": null,
      "user_name": null,
      "participant_id": "66666666-7777-8888-9999-000000000000",
      "join_time": 1549391714,
      "duration": 1650
    }
  ]
}
```

A meeting session is a set of one or more people in a room together during a specific time window.

Meeting session objects contain information about who joined calls in your rooms, when, and for how long.

Each meeting session object has six fields:

* A unique, opaque meeting session `id`
* The name of the `room`
* A `start_time` (when the first user joined the session)
* A `duration`
* An `ongoing` boolean (true, if any participants are currently in the room)
* A `max_participants` value (number), for the maximum number of participants that were present in the meeting at one time
* A list of meeting session `participants`

The objects in the `participants` list five fields: `join_time`, `duration`, `participant_id`, `user_id`, and `user_name`. `join_time`, `duration`, and `participant_id` will always contain valid data. `user_id` and `user_name` fields will be `null` if that information is not available for the participant.

The `start_time` and `join_time` fields are unix timestamps (seconds since the epoch), and have approximately 15-second granularity. (We generally do not write a "meeting join" record until a user has stayed in a room for at least 10 seconds. ) The `duration` fields are elapsed times in seconds.

Because rooms are often reused, the definition of a meeting session needs to account for what happens when people join and leave rooms in arbitrary sequences. Here are the rules that determine the start and end bounds of a meeting session:
A new meeting session begins when:

* A single participant joins the room and has been alone for 30 seconds.
* A second participant joins the room prior to the 30 seconds.
* A participant remains in a room alone for 10 minutes after all others have left

A meeting session ends when:

* All users leave the room. (The participant count is zero)
* A participant remains in a room alone for 10 minutes after all others have left. (The participant count decrements to 1 for 10 minutes)

The intent of 10 minute reset is to try to match users expectations about what a "meeting" is. Some of our users leave rooms open for long periods of time, and stay in that room, and then are periodically joined by other people for "meetings." Thus, a user's unbroken time in a room might span multiple meeting sessions.

```bash theme={null}
# Example: get information about the 5 most recent meetings in classroom-104
curl -H "Content-Type: application/json" \
     -H "Authorization: Bearer DAILY_API_KEY" \
     https://api.daily.co/v1/meetings?room=classroom-104&limit=5
```