Meetingize for developers
Meetingize turns real conversations (in person, by phone or video) into diarized, timestamped transcripts, AI meeting reports and professional documents. The developer platform exposes the same data and actions to your code and to AI assistants, always within the secure context of one Meetingize account.
What can I build?
Section titled “What can I build?”- Sync meetings into your tools: push transcripts, reports and action items into a CRM, a case management system or a data warehouse as soon as they are ready (webhooks + REST API).
- Transcribe from your own app: upload an audio or video file, or give a URL, and get back a diarized transcript
and an AI report (
POST /v1/meetings). - Generate documents: produce minutes, follow-up emails, suitability reports or any custom document from a
meeting, with Meetingize templates or your own prompt (
POST /v1/meetings/{id}/documents). - Give your AI assistant a memory of your meetings: connect Claude, ChatGPT, Cursor or any MCP client to the Meetingize MCP server and ask questions across all your meetings.
The building blocks
Section titled “The building blocks”| Block | What it is | Page |
|---|---|---|
| REST API v1 | JSON over HTTPS, cursor pagination, RFC 9457 errors, idempotent POSTs | API overview |
| Authentication | API keys (mtgz_...) or OAuth 2.1 access tokens, both with scopes | Authentication |
| Asynchronous jobs | Meeting processings and document generations run as jobs you can poll | Jobs |
| Webhooks | Signed event notifications with retries | Webhooks |
| Usage billing | Monthly API allowance included in your plan, then optional on-demand billing | Billing |
| MCP server | Remote MCP server (Streamable HTTP + OAuth 2.1) for AI assistants | MCP overview |
| CLI | meetingize command line, built on the API | CLI |
Principles
Section titled “Principles”- Your data only. Every credential belongs to one Meetingize user and only sees that user’s meetings and
documents. Other accounts’ resources answer
404, never403. - Least privilege. Keys and OAuth connections carry scopes (
read:meetings,read:transcripts,write:documents…). Give each integration only what it needs. - Pay for what you use. API usage is metered from real consumption (audio minutes, LLM tokens) and first debited from the allowance included in your plan. It never eats your web app quotas.
Next: the quickstart.