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

# Get meeting by ID



## OpenAPI

````yaml /openapi.yaml get /meetings/{id}
openapi: 3.0.3
info:
  title: Screenpipe API
  version: 1.0.0
  description: >-
    Screenpipe captures everything you see, say, and hear on your computer. Use
    this API to search through captured content, manage recordings, and build
    AI-powered automations on top of your screen data.


    The server runs locally at `http://localhost:3030` by default.
servers: []
security: []
tags:
  - name: Search
    description: Search through captured screen and audio content
  - name: Frames
    description: Access captured screenshots and their extracted text
  - name: Elements
    description: Query captured UI accessibility tree data
  - name: Audio
    description: Manage audio recording devices
  - name: Vision
    description: Manage screen capture monitors
  - name: Meetings
    description: Detected and manual meeting transcriptions
  - name: Speakers
    description: Speaker identification and management
  - name: Memories
    description: AI-extracted knowledge from screen activity
  - name: Tags
    description: Tag content items for organization
  - name: Activity
    description: Activity summaries and analytics
  - name: Vault
    description: Encrypt/decrypt all data at rest
  - name: Cloud Sync
    description: Sync data across devices via cloud
  - name: Cloud Archive
    description: Archive old data to cloud storage
  - name: Data Retention
    description: Auto-delete old data locally
  - name: Data Management
    description: Manual data deletion and storage info
  - name: Database
    description: Direct database access
  - name: System
    description: Health checks and system status
  - name: Experimental
    description: Experimental/unstable endpoints
paths:
  /meetings/{id}:
    get:
      tags:
        - Meetings
      summary: Get meeting by ID
      operationId: routes_meetings_get_meeting_handler
      parameters:
        - name: id
          schema:
            type: integer
          in: path
          required: true
          style: simple
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MeetingRecord'
components:
  schemas:
    MeetingRecord:
      type: object
      properties:
        id:
          type: integer
        meeting_start:
          type: string
        meeting_end:
          nullable: true
          type: string
        meeting_app:
          type: string
        title:
          nullable: true
          type: string
        attendees:
          nullable: true
          type: string
        note:
          nullable: true
          type: string
        detection_source:
          type: string
        created_at:
          type: string
      required:
        - id
        - meeting_start
        - meeting_end
        - meeting_app
        - title
        - attendees
        - note
        - detection_source
        - created_at

````