Meetily
Agent APIReference

Meetings

List, read, export, rename, delete meetings, and manage summaries and speaker labels.

Meetings are the core resource. You can list and read them, export, rename, delete, read and overwrite summaries, regenerate a summary, and set speaker labels. Note: you cannot create a meeting over the API; meetings come from the recording flow.

Endpoints

Method + pathScopeNotes
GET /v1/meetingsReadPagination via ?limit(max 200, default 50) and ?offset.
GET /v1/meetings/:idReadReturns a single MeetingDto.
GET /v1/meetings/:id/transcriptReadReturns {meeting_id,title,segments:[...]}.
GET /v1/meetings/:id/summaryReadReturns {meeting_id,status,result?,error?,updated_at}.
GET /v1/meetings/:id/exportRead?format=json|md|txt, default json.
GET /v1/search?q=ReadFull-text search across meetings. Capped (?limit default 50, max 200) and returns {results} only, with no total - unlike GET /v1/meetings, a client cannot tell whether results were truncated, so widen q or raise limit if you may be at the cap.
PATCH /v1/meetings/:idWriteRename. Body {title}, title max 500 chars.
DELETE /v1/meetings/:idDeleteIrreversible. Cascades to the meeting's transcript and summary.
PUT /v1/meetings/:id/summaryWriteOverwrites the summary text.
POST /v1/meetings/:id/summary/regenerateWriteReturns 202 with a process_id. 422 if the transcript is empty. Default template daily_standup.
PUT /v1/meetings/:id/speaker-labelsWriteMaps cluster keys to display names.

Irreversible - read first, confirm, least privilege

This resource has destructive operations. DELETE /v1/meetings/:id permanently removes the meeting and cascades to its transcript and summary; PUT .../summary overwrites the existing summary. Read the target first, confirm with the operator before acting, and never wrap a delete in an unbounded loop over all meetings. Deletion requires the delete scope by design.

List meetings

curl -s "http://127.0.0.1:8420/v1/meetings?limit=20" -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

Export a meeting

curl -s "http://127.0.0.1:8420/v1/meetings/MEETING_ID/export?format=md" -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

Regenerate a summary

Regenerating a summary does not block. The call returns 202 with a process_id immediately, and the summary updates asynchronously once the job finishes.

curl -s -X POST http://127.0.0.1:8420/v1/meetings/MEETING_ID/summary/regenerate -H "Authorization: Bearer $MEETILY_PRO_TOKEN" -H "content-type: application/json" -d '{"template_id":"daily_standup"}'

Last updated on

On this page