Read AI REST API

Open-beta public REST API for programmatic access to a user's Read AI meeting data. Three documented meeting endpoints — list meetings with cursor pagination and epoch-millisecond time filters, retrieve a meeting by ULID, and retrieve live data for an in-progress meeting — plus an expand[] projection covering summary, chapter_summaries, action_items, key_questions, topics, transcript, metrics and recording_download. Read-only; every documented operation is a GET. Bearer-token authenticated via OAuth 2.1 with dynamic client registration.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/read-ai-rest-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
name: Read AI REST API
description: Open-beta public REST API for programmatic access to a user's Read AI meeting data. Three
  documented meeting endpoints — list meetings with cursor pagination and epoch-millisecond time filters,
  retrieve a meeting by ULID, and retrieve live data for an in-progress meeting — plus an expand[] projection
  covering summary, chapter_summaries, action_items, key_questions, topics, transcript, metrics and recording_download.
  Read-only; every documented operation is a GET. Bearer-token authenticated via OAuth 2.1 with dynamic
  client registration.
humanURL: https://support.read.ai/hc/en-us/articles/49381161088659-API-Reference
baseURL: https://api.read.ai/
image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
tags:
- Meetings
- Transcription
- Meeting Intelligence
- REST
properties:
- type: Documentation
  url: https://support.read.ai/hc/en-us/articles/49381161088659-API-Reference
- type: APIReference
  url: https://support.read.ai/hc/en-us/articles/49381161088659-API-Reference
- type: GettingStarted
  url: https://support.read.ai/hc/en-us/articles/49379985941523-Read-AI-API-and-MCP-Overview
- type: Authentication
  url: authentication/read-ai-authentication.yml
- type: OAuthScopes
  url: scopes/read-ai-scopes.yml
- type: ErrorCatalog
  url: errors/read-ai-problem-types.yml
- type: RateLimits
  url: rate-limits/read-ai-rate-limits.yml
- type: Conventions
  url: conventions/read-ai-conventions.yml
- type: DataModel
  url: data-model/read-ai-data-model.yml
x-evidence:
  verified: '2026-08-05'
  docs_describe: Method + path, query parameters, request examples, response examples, pagination contract
    and an error-code table for GET /v1/meetings, GET /v1/meetings/{id} and GET /v1/meetings/{id}/live.
  endpoint_check: GET https://api.read.ai/v1/meetings -> 401 {"detail":"Not authenticated"}
  openapi: None published. /openapi.json, /docs and /redoc are 301-redirected by the ALB to https://www.read.ai/;
    /openapi.yaml, /swagger.json, /v1/openapi.json, /api-docs return {"detail":"Not Found"}.