Skip to main content
POST
Meetings

Overview

Read-only tools on a connected meeting recorder (Connections): Granola and Fireflies. An agent reads what was said and promised in a meeting, for example the follow-ups after a client meeting. No meeting starts a goal; a goal reads meetings when it runs.
  • POST /v1/tools/meetings/list (meetings_list): meetings with title, start, duration and participants.
  • POST /v1/tools/meetings/get (meetings_get): one meeting’s summary and action items, and its transcript when asked for.
Both take connection_id: list your connections (GET /v1/connections or oneshot_connections_list) and pick by system and account_label. Titles, participants, summaries and transcripts are returned in the answer only; OneShot never stores or logs them. A goal gets them in memory: its history keeps no copy, so a later step reads the meeting again.

Granola and Fireflies

Granola connects with a sign-in. Granola returns the signed-in user’s own notes, notes shared with them and notes in folders shared with the workspace, on Granola plans that allow API access. Transcripts need a paid plan. Granola states local start times without an offset and no duration. Fireflies connects with your Fireflies API key, stored encrypted and deleted on revoke.

Request

Paid with x402 (payment-signature). Refusals for the body or the connection come before payment and are not charged.

Response (200)

array
Each meeting: id, title, started_at, duration_s, participants (name, email) and source (system, id), with next_cursor (null on the last page). With a query, a page can hold fewer than limit meetings.
object
Get: the meeting, plus summary, action_items (text, owner) and transcript (speaker, text, at in seconds). A part not in include is absent.

Errors