Reference

Transcript

2 routes, generated from Morse’s own OpenAPI document. Every path below hangs off the base URL, and every one needs the bearer header.

The examples are built from each route’s schema, so the shapes and types are exactly what the API declares. The values are illustrative, and no one has run them.

Whole meeting, turn-grouped.

GET/meetings/{meeting_id}/transcript

Refetched in full on every nudge: at a few hundred turns an hour that is cheaper than a cursor protocol (§8 rule 1).

GET/meetings/{meeting_id}/transcript

curl "$MORSE/meetings/3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60/transcript" \
  -H "Authorization: Bearer $MORSE_TOKEN"

200

[
  {
    "content": "Annual plans are billed up front.",
    "ended_at": "2026-10-02T10:30:00+05:30",
    "participant_id": "3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60",
    "segment_ids": [
      "3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60"
    ],
    "speaker_name": "Priya Shah",
    "started_at": "2026-10-02T10:30:00+05:30"
  }
]

The transcript as it is written, as server-sent events.

GET/meetings/{meeting_id}/transcript-events

While the meeting is live, the host and the signed-in members in the room; afterwards, whoever the notes are shared with.

GET/meetings/{meeting_id}/transcript-events

curl "$MORSE/meetings/3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60/transcript-events" \
  -H "Authorization: Bearer $MORSE_TOKEN"