---
title: "Fetch details of an active session"
method: GET
path: "/meetings/{meeting_id}/active-session"
tags: ["Active session"]
---

# Fetch details of an active session

`GET /meetings/{meeting_id}/active-session`

Returns details of an ongoing active session for the given meeting ID.

## Path parameters

- `meeting_id` string, required

## Response `200`

Active Session Success response

- object
  - `success` boolean
  - `data` ActiveSession
    - `id` string, required — ID of the session
    - `associated_id` string, required — ID of the meeting this session is associated with. In the case of V2 meetings, it is always a UUID. In V1 meetings, it is a room name of the form `abcdef-ghijkl`
    - `meeting_display_name` string, required — Title of the meeting this session belongs to
    - `type` 'meeting' | 'livestream' | 'participant', required — type of session
    - `status` 'LIVE' | 'ENDED', required — current status of session
    - `live_participants` number, required — number of participants currently in the session
    - `max_concurrent_participants` number, required — number of maximum participants that were in the session
    - `minutes_consumed` number, required — number of minutes consumed since the session started
    - `organization_id` string, required — Organization id that hosted this session
    - `started_at` string, required — timestamp when session started
    - `created_at` string, required — timestamp when session created
    - `updated_at` string, required — timestamp when session was last updated
    - `ended_at` string — timestamp when session ended
    - `meta` object — Any meta data about session.
    - `breakout_rooms` ActiveSession[]

## Other responses

- `404` — Active Session is not found for the given meetingId

---

[API](https://skmtc.net/dyte-io/apis/dyte-rest-apis.md) · [All operations](https://skmtc.net/dyte-io/apis/dyte-rest-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/dyte-io/dyte-rest-apis/revisions/f62d3edd92ae/schema)