Meetings and transcripts

A meeting is one recording or import in Meetingize: its metadata, the diarized transcript, the AI meeting report (called summary in the API) and the documents generated from it. Meetings are identified by a UUID.

To create a meeting from a recording, see Create a meeting and get the results.

How do I list or search meetings?

GET /v1/meetings returns your meetings, most recent first, optionally filtered.

GET /v1/meetings?q=budget&client=Dupont&tag=rdv&recorded_after=2026-07-01T00:00:00Z&status=completed&limit=20

Parameter	Description
q	case-insensitive text search in the title, the AI report and the transcript
tag	tag name, repeatable (tag=a&tag=b)
client	client folder name
recorded_after, recorded_before	date of the meeting (ISO 8601 date-times)
created_after, created_before	date it was added to Meetingize
status	draft, queued, processing, completed, failed
limit, cursor	pagination

Each meeting has id, title, status, recorded_at, created_at, transcribe_only, duration_seconds, language, source, recording_type, tags, client, has_transcript, has_summary and web_url (link to open it in the web app).

Meeting status

Status	Meaning
draft	being recorded in the web or mobile app, no audio finalized yet
queued	waiting for processing
processing	transcription, then AI report (the transcript is readable as soon as has_transcript is true)
completed	transcript and AI report available (transcript only for transcribe_only meetings)
failed	processing failed

Meeting details

GET /v1/meetings/{id} returns one meeting with everything about it: its summary (AI report), its participants, the list of generated documents and, for meetings created through the API, its latest processing job.

PATCH /v1/meetings/{id} updates the title, the date, the tags and the participants (scope write:meetings), and DELETE /v1/meetings/{id} permanently deletes the meeting with its recording and documents. Examples in step 6 of the guide.

Transcript

GET /v1/meetings/{id}/transcript returns the diarized, timestamped transcript.

GET /v1/meetings/{id}/transcript?format=json

Scope read:transcripts. The JSON format returns the language, duration, the list of speakers and the segments:

{
  "object": "transcript",
  "meeting_id": "1b9e...",
  "language": "fr",
  "speakers": ["SPEAKER_00", "SPEAKER_01"],
  "segments": [
    { "start": 4.5, "end": 9.0, "speaker": "SPEAKER_01", "speaker_name": "Mme Martin",
      "text": "Merci. Le budget est validé pour le trimestre." }
  ]
}

speaker is the diarization label; speaker_name is filled when the speaker was identified in Meetingize. Other formats: md (Markdown), txt ([hh:mm:ss] Speaker: text lines), srt and vtt (subtitles, the VTT includes <v Speaker> voice tags). While transcription is still running the endpoint answers 409 transcript_not_ready.

AI meeting report

GET /v1/meetings/{id}/summary returns the AI meeting report.

GET /v1/meetings/{id}/summary?format=json   # or format=md

Returns the report in Markdown (markdown) and, when available, the structured result produced by the AI (summary, minutes, key takeaways, action items, speaker identification). 409 summary_not_ready while processing.

Participants

GET /v1/meetings/{id}/participants lists the people of the meeting with their id (par_<n>), name, email and the speaker_labels attributed to them. Speakers of the transcript not yet attributed to anyone are listed with id: null. Attribute them with PATCH /v1/meetings/{id}.

LLM-ready export

GET /v1/meetings/{id}/export bundles everything about a meeting into text ready to paste into an LLM.

GET /v1/meetings/{id}/export?format=md&max_tokens=24000&lang=en

Scopes read:meetings and read:transcripts. Bundles a priming prompt, the metadata, the participants, the AI report and the diarized timestamped transcript, split into parts of at most max_tokens tokens (2,000 to 200,000, default 24,000) so each part fits in a model context window. lang (fr default, or en) sets the language of the priming prompt. format=json returns parts[] with index, total, tokens and content; format=md concatenates the parts with --- Part i/n --- separators.

This is the export to paste into ChatGPT or Claude by hand. To let your assistant fetch meetings itself, use the MCP server.