Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.auvy.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Meetings API

Meetings are versioned resource objects in the collaboration vertical. They share the same resource head, grep, search, and Vault browse substrate as other resource kinds.
Meetings are brain-scoped. Send X-Brain-Id, a brain_id query/body field, or configure SDK getBrainId.

​
List Meetings

GET /v1/meetings
Returns resource-head list rows for the active brain. 
const meetings = await auvy.resources.meetings.list({ limit: 50 })

​
Create Meeting

POST /v1/meetings
FieldTypeRequiredDescription
titlestringYesMeeting title.
descriptionstringNoShort description.
bodyobjectNoPartial structured body: agenda, notes, summary, decisions, action items, transcript refs.
brain_idstringNoBrain UUID when not supplied by auth context.
curl -X POST https://api.auvy.ai/v1/meetings \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-Brain-Id: YOUR_BRAIN_ID" \
  -H "Content-Type: application/json" \
  -d '{"title":"Customer sync","body":{"agenda":["Renewal risks","Next steps"]}}'

​
Get Meeting

GET /v1/meetings/:id

​
Patch Meeting Body

Structured meeting patches use the central resource patch route: 
await auvy.resources.meetings.patchPartial(meetingId, {
  summary: 'Customer wants a renewal proposal by Friday.',
  decisions: ['Send proposal draft'],
})

​
Live Transcription

POST /v1/meetings/:id/transcription/live/start
POST /v1/meetings/:id/transcription/chunk
GET  /v1/meetings/:id/transcription/live/events/:session_id
GET  /v1/meetings/:id/transcription/live/history
POST /v1/meetings/:id/transcription/live/stop
GET  /v1/meetings/:id/transcription/artifacts/:artifact_id
After live/start, send ordered linear16 PCM with POST .../transcription/chunk (job_id, monotonic seq, chunk_base64). The API stores each chunk for finalize and forwards the same audio to the live Deepgram session (live captions use the SSE stream below). Live events are server-sent events. Final transcripts are persisted as artifacts so they can be read, searched, edited, and referenced like other document-lane resources.