​

Live Lecture API

Route: /api/groups/live-lecture

Documentation for the live lecture API endpoint will be added here.

​

Live Lecture Analytics API

Route: POST /api/groups/live-lecture

Get analytics data for live lecture usage by students within a group, including sessions created and chat messages sent during live lectures with optional student-level breakdowns.

​

Authentication

This endpoint requires authentication using an API key.

Header Required:

x-api-key: YOUR_API_KEY

​

Parameters

​

Query Parameters

​

Response Format

​

Group-Level Data (students=false)

Returns aggregated live lecture analytics for the entire group.

{
  "success": true,
  "reports": [
    {
      "startDate": "2025-01-01T00:00:00.000Z",
      "endDate": "2025-01-07T23:59:59.999Z",
      "numStudentsUsed": 25,
      "data": [
        {
          "title": "Sessions Made",
          "value": 48
        },
        {
          "title": "Chat Messages",
          "value": 892
        }
      ]
    }
  ]
}

​

Student-Level Data (students=true)

Returns individual student live lecture analytics.

{
  "success": true,
  "reports": [
    {
      "startDate": "2025-01-01T00:00:00.000Z",
      "endDate": "2025-01-07T23:59:59.999Z",
      "studentName": "John Doe",
      "studentId": "user_123456",
      "data": [
        {
          "title": "Sessions Made",
          "value": 3
        },
        {
          "title": "Chat Messages",
          "value": 47
        }
      ]
    }
  ]
}

​

Data Fields Explained

​

Live Lecture Metrics

• Sessions Made: Number of live lecture sessions created by students
• Chat Messages: Number of chat messages sent during live lecture sessions

​

Additional Fields

• numStudentsUsed (Group-level only): Number of unique students who used live lecture features
• studentName (Student-level only): Display name of the student
• studentId (Student-level only): Unique identifier for the student

​

Error Responses

​

403 Unauthorized

Returned when API key is missing or invalid.

{
  "error": "Unauthorized"
}

Causes:

• Missing x-api-key header
• Invalid API key
• API key not associated with a valid group plan

​

400 Bad Request

Returned when required parameters are missing.

{
  "error": "Missing params"
}

​

Notes

• Reports are automatically sorted by start date in ascending order
• Date ranges are inclusive of both start and end dates
• All timestamps should be in ISO 8601 format