Skip to content

Documents and templates

Meetingize generates documents from a meeting: minutes, follow-up emails, proposals, suitability reports and any custom document. Generation runs as an asynchronous job and consumes LLM tokens billed on your API usage.

GET /v1/personas
GET /v1/templates?persona=INSURANCE_BROKER
GET /v1/templates/{template_id}

Templates (tpl_<n>) are grouped by professional persona (INSURANCE_BROKER, FINANCIAL_ADVISOR, ATTORNEY, PROJECT_MANAGER…). Each template has an id, name, description, icon and persona.

POST /v1/meetings/{meeting_id}/documents
Idempotency-Key: 6f1d...
Content-Type: application/json
{ "template_id": "tpl_42", "title": "Rapport d'adéquation", "instructions": "Mention the client's risk profile." }
FieldDescription
template_ida template id; mutually exclusive with prompt
promptyour own generation instructions (up to 20,000 characters) instead of a template
titledocument title (up to 300 characters)
instructionsextra instructions appended to the template (up to 5,000 characters)
include_transcriptinclude the full transcript in the context (default true)
metadatayour own JSON object, echoed in the job and webhook events

Exactly one of template_id or prompt is required. The response is 202 Accepted with a job of kind document_generation. When the job is completed its document_id is set and a document.generated webhook is sent (document.failed on error).

Documents generated through the API do not count against the document quota of your web app plan: they are billed on API usage instead.

GET /v1/documents?meeting_id={meeting_id}
GET /v1/documents/{document_id}?format=json # metadata + markdown
GET /v1/documents/{document_id}?format=md # text/markdown
GET /v1/documents/{document_id}?format=pdf # application/pdf
GET /v1/documents/{document_id}?format=docx # Word

Scope read:documents. Documents marked as private by another participant of a shared meeting are not listed.