Read AI offers a public REST API, which is ideal for developers looking to build applications that programmatically access their Read AI meeting data. It is currently available as an open beta release.

⚠️ Before starting, make sure you have reviewed the prerequisites.

• Authentication
• Meeting States
• Endpoints
  • 1. List Meetings
  • 2. Retrieve a Meeting
  • 3. Retrieve a Live Meeting
• Expandable Fields
• Pagination
• Error Codes

Authentication

All endpoints require Bearer token authentication using the Authorization header. See API Keys & Authentication for instructions on how to obtain your access token.

Header Format

Authorization: Bearer YOUR_ACCESS_TOKEN

Example

curl https://api.read.ai/v1/meetings \
  -H "Authorization: Bearer sk_test_123" \
  -H "Accept: application/json"

For JWTs (used in OAuth2/Ory), Bearer would look like: 

"Authorization: Bearer ory_at_..."

Meeting States

Meetings in the Read AI API can be in different states:

• Active Meeting: A meeting currently in progress. Identified by end_time_ms being not present or null.
• Ended Meeting: A completed meeting. Identified by end_time_ms having a value.
• Live-Enabled Meeting: A meeting with real-time data capture enabled. Identified by live_enabled: true. 

Endpoints

The base URL for all endpoints is https://api.read.ai/.

1. List Meetings

Method: GET /v1/meetings

Description: Returns a paginated list of meetings in reverse chronological order (newest first), optionally filtered by start time. This endpoint returns both active and ended meetings, including their live-enabled status. Note that active meetings will have limited or no data for expandable fields, as these are generated after a meeting concludes.

Query Parameters

Example Request

curl "https://api.read.ai/v1/meetings?limit=5&start_time_ms.gte=1733700000000" \
  -H "Authorization: Bearer sk_test_123" \
  -H "Accept: application/json"

Example Response

{
  "object": "list",
  "url": "/v1/meetings",
  "has_more": false,
  "data": [
    {
      "id": "01HFYH0A6JM4R7MZ2E6X5T9BNP",
      "start_time_ms": 1733800000000,
      "end_time_ms": 1733803600000,
      "scheduled_start_time_ms": 1733799800000,
      "scheduled_end_time_ms": 1733803400000,
      "participants": [
        {
          "name": "Alice Example",
          "email": "alice@example.com",
          "invited": true,
          "attended": true
        }
      ],
      "owner": {
        "name": "Alice Example",
        "email": "alice@example.com"
      },
      "title": "Weekly status sync",
      "report_url": "https://app.read.ai/analytics/meetings/01HFYH0A6JM4R7MZ2E6X5T9BNP",
      "platform": "zoom",
      "platform_id": "987654321",
      "folders": ["Weekly Sync"],
      "live_enabled": false
    }
  ]
}

2. Retrieve a Meeting

Method: GET /v1/meetings/{id}

Description: Fetch a specific meeting by its unique ID. For active, live-enabled meetings, use the /v1/meetings/{id}/live endpoint instead.

Path Parameters

Query Parameters

Example Request

curl "https://api.read.ai/v1/meetings/01HFYH0A6JM4R7MZ2E6X5T9BNP?expand[]=summary&expand[]=metrics" \
  -H "Authorization: Bearer sk_test_123" \
  -H "Accept: application/json"

Example Response

{
  "id": "01HFYH0A6JM4R7MZ2E6X5T9BNP",
  "start_time_ms": 1733800000000,
  "end_time_ms": 1733803600000,
  "scheduled_start_time_ms": 1733799800000,
  "scheduled_end_time_ms": 1733803400000,
  "participants": [
    {
      "name": "Alice Example",
      "email": "alice@example.com",
      "invited": true,
      "attended": true
    }
  ],
  "owner": {
    "name": "Alice Example",
    "email": "alice@example.com"
  },
  "title": "Weekly status sync",
  "report_url": "https://app.read.ai/analytics/meetings/01HFYH0A6JM4R7MZ2E6X5T9BNP",
  "platform": "zoom",
  "platform_id": "987654321",
  "folders": ["Weekly Sync"],
  "live_enabled": false,
  "summary": "We reviewed project timelines and assigned new action items.",
  "metrics": {
    "read_score": 0.9,
    "sentiment": 0.3,
    "engagement": 0.75
  }
}

3. Retrieve a Live Meeting

Method: GET /v1/meetings/{id}/live

Description: Retrieve live meeting data for an ongoing meeting by its unique ID. This endpoint allows you to fetch real-time transcript and chapter summaries as the meeting progresses, with optional filtering by start time.

Important Note: All meetings do not have live data by default, it is only available if you have the live dashboard open during the meeting. We will be adding an account setting to enable live data for all meetings as part of the full GA release. 

Path Parameters

Query Parameters

Example Request

curl "https://api.read.ai/v1/meetings/01HFYH0A6JM4R7MZ2E6X5T9BNP/live?expand[]=transcript&start_time_ms.gte=1733800000000" \
  -H "Authorization: Bearer sk_test_123" \
  -H "Accept: application/json"

Example Response

{
  "id": "01HFYH0A6JM4R7MZ2E6X5T9BNP",
  "start_time_ms": 1733800000000,
  "end_time_ms": null,
  "scheduled_start_time_ms": 1733799800000,
  "scheduled_end_time_ms": 1733803400000,
  "participants": [
    {
      "name": "Alice Example",
      "email": "alice@example.com",
      "invited": true,
      "attended": true
    }
  ],
  "owner": {
    "name": "Alice Example",
    "email": "alice@example.com"
  },
  "title": "Weekly status sync",
  "report_url": "https://app.read.ai/analytics/meetings/01HFYH0A6JM4R7MZ2E6X5T9BNP",
  "platform": "zoom",
  "platform_id": "987654321",
  "folders": ["Weekly Sync"],
  "live_enabled": true,
  "transcript": {
    "speakers": [
      {
        "name": "Alice Example"
      }
    ],
    "turns": [
      {
        "speaker": {
          "name": "Alice Example"
  },
        "text": "Let's start with the project updates.",
        "start_time_ms": 1733800000000,
  "end_time_ms": 1733800005000
      }
    ],
    "text": "[Alice Example]: Let's start with the project updates."
  }
}

Expandable Fields

The API supports the expand[] parameter to fetch additional enriched fields that are not included by default. Note that using expanded fields will increase response times as the API retrieves and processes additional data. Expanding multiple fields or using expansions on large list requests may result in noticeably slower processing times.

Available Fields

• summary
• chapter_summaries
• action_items
• key_questions
• topics
• transcript
• metrics
• recording_download

Example Request

curl "https://api.read.ai/v1/meetings?expand[]=metrics&expand[]=transcript" \
  -H "Authorization: Bearer sk_test_123" \
  -H "Accept: application/json"

Pagination

The API uses cursor-based pagination for navigating through large result sets.

Parameters

Response Fields

{
  "object": "list",
  "url": "/v1/meetings",
  "has_more": true,
  "data": [
    {
      "id": "01KG7BZV04HJGVBM4KJCWV9P4N",
      "title": "Team Standup",
      ...
    },
    {
      "id": "01KG76TMYXDRZ0D86Z3MNXP566",
      "title": "Client Call",
      ...
    },
    ...
    {
      "id": "01KG4JRNA0EEFAJTM0S3PMDARK",  // ← Last meeting id in this page
      "title": "Sprint Planning",
      ...
    }
  ]
}

Error Codes

Common error responses follow standard HTTP status codes.