meetingize CLI

meetingize is a small command line client for the Meetingize API. It is a single Python file (Python 3.8 or later, no dependency), handy for scripts, cron jobs and quick checks.

Install

curl -fsSL -o ~/.local/bin/meetingize https://docs.meetingize.com/cli/meetingize.py
chmod +x ~/.local/bin/meetingize
meetingize --version

(Any directory of your PATH works. On Windows run it with python meetingize.py ....)

Log in

Create an API key in Settings > Developers, then:

meetingize login                 # prompts for the key, checks it, stores it in ~/.config/meetingize/config.json (mode 600)
meetingize whoami

Alternatively set the MEETINGIZE_API_KEY environment variable.

Commands

Command	What it does
meetingize meetings [-q TEXT] [--client NAME] [--tag T] [--since DATE] [--until DATE] [--status S] [--limit N]	list or search meetings
meetingize show MEETING_ID	metadata, participants, AI report, documents
meetingize transcript MEETING_ID [--format md|txt|srt|vtt|json] [-o FILE]	diarized transcript
meetingize export MEETING_ID [--max-tokens N] [--lang fr|en] [-o FILE]	LLM-ready export (Markdown, in parts)
meetingize templates [--persona ID]	document templates
meetingize generate MEETING_ID (--template TPL | --prompt TEXT) [--title T] [--wait] [-o FILE]	generate a document (billed)
meetingize documents [--meeting ID]	list documents
meetingize document DOC_ID [--format md|pdf|docx|json] [-o FILE]	download a document
meetingize create FILE | --url URL [--title T] [--recorded-at DATE] [--language fr] [--tag T] [--template TPL] [--persona ID] [--transcribe-only] [--wait]	create a meeting from a recording, optionally with documents (billed)
meetingize feedback MESSAGE [--type bug|feature_request|question|feedback] [--meeting ID]	report a bug or send feedback to the Meetingize team
meetingize job JOB_ID [--wait]	job status
meetingize usage	API consumption of the month
meetingize webhooks verify --secret whsec_... --header 't=...,v1=...' --body FILE	check a webhook signature locally

Most listing commands accept --json for machine-readable output. Every POST is sent with a fresh Idempotency-Key.

Examples

# All meetings with client Dupont since July, then the transcript of the latest one as subtitles
meetingize meetings --client Dupont --since 2026-07-01T00:00:00Z
meetingize transcript 1b9e... --format srt -o rdv.srt

# Send a recording, generate a document after the report, and wait
meetingize create ./rdv-client.m4a --title "RDV Dupont" --language fr --template tpl_42 --wait

# Generate a follow-up email and print it
meetingize generate 1b9e... --prompt "Follow-up email with decisions and next steps" --wait

# Report a bug
meetingize feedback "The SRT export of meeting 1b9e... is empty" --type bug --meeting 1b9e...

# Paste a meeting into any chatbot
meetingize export 1b9e... --lang en | pbcopy

Exit codes

0 on success, a non-zero code with the API error (HTTP 404 not_found: ...) otherwise. webhooks verify exits 1 when the signature is invalid.