Meetings

12 operations in the Tolvi API, version 1. Paths are relative to https://api.tolvi.co.uk. Every amount is integer pence.

List meetings

GET/api/v1/meetings

Scopes: meetings:read

Newest first (up to 200). Filter by client to see the meetings filed against it, by words in the title or client name, by status, or to the ones you sent. Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for GET /api/v1/meetings
Name	In	Type	Description
`mine`	query	`string`	true: only the meetings you sent a note-taker to. One of: `true`, `false`
`status`	query	`string (MeetingStatusGroup)`	upcoming (scheduling, scheduled), in_progress (joining to processing), ready, not_recorded (failed or cancelled). One of: `upcoming`, `in_progress`, `ready`, `not_recorded`
`q`	query	`string`	Words in the meeting’s title or its client’s name. up to 100 characters
`clientId`	query	`string (uuid)`

Responses

200 OK, `application/json`

Body: array of MeetingSummary.

A meeting a note-taker was sent to.

200 OK response for GET /api/v1/meetings
Field	Type	Description
`[].id`required	`string (uuid)`
`[].title`required	`string`
`[].clientId`required	`string (uuid)`nullable
`[].clientName`required	`string`nullable
`[].platform`required	`string (MeetingPlatform)`nullable	One of: `zoom`, `google_meet`, `microsoft_teams`, `webex`, `goto_meeting`
`[].meetingUrl`required	`string (uri)`
`[].joinAt`required	`string (date-time)`
`[].source`required	`string (MeetingSource)`	link: pasted on the Meetings page. calendar: ticked on the Calendar page. One of: `link`, `calendar`
`[].status`required	`string (MeetingStatus)`	scheduling: being sent to Recall. scheduled: will join at joinAt. joining, waiting_room (someone must admit it), in_call, recording. processing: the call ended; the transcript and summary are on their way. ready: transcript and summary filed. failed: see statusDetail. cancelled. One of: `scheduling`, `scheduled`, `joining`, `waiting_room`, `in_call`, `recording`, `processing`, `ready`, `failed`, `cancelled`
`[].statusDetail`required	`string`nullable	Why it failed or is held up, in words.
`[].startedAt`required	`string (date-time)`nullable
`[].endedAt`required	`string (date-time)`nullable
`[].createdById`required	`string (uuid)`nullable
`[].createdByName`required	`string`nullable
`[].outputStatus`required	`string (MeetingOutputStatus)`	One of: `pending`, `transcribing`, `summarising`, `ready`, `failed`
`[].actionCount`required	`integer`	at least 0
`[].openActionCount`required	`integer`	Next steps not yet sorted with Create follow-ups (made into a review point or a client request, or skipped). at least 0
`[].recordingDeletedAt`required	`string (date-time)`nullable	When the recording (audio and video) was deleted at Recall. Tolvi keeps only the transcript and summary.
`[].billableMinutes`required	`integer`nullable	Minutes this meeting counts against the firm’s monthly allowance: the recording’s length, rounded up. Null until it ends. at least 0

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 429 Too many requests, as problem details (application/problem+json).

Send a note-taker to a meeting

POST/api/v1/meetings

Scopes: meetings:write
Retries: Send an Idempotency-Key to make retries safe.

Recall.ai joins the meeting at joinAt (now if left out) as a visible participant, posts a notice that it is recording, and records it. After the call Tolvi files the transcript and Tolvi AI’s summary and actions against the meeting (charged to you as AI tokens). 409 if someone in the firm already sent one to the same meeting; 502 if Recall refused it. Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for POST /api/v1/meetings
Name	In	Type	Description
`Idempotency-Key`	header	`string`	A unique key (1-255 visible characters) to make retries safe. Replayed for 24 hours. 1 to 255 characters

Request body

Required. application/json: object (LaunchMeetingRequest).

Request body for POST /api/v1/meetings
Field	Type	Description
`meetingUrl`required	`string (uri)`	A Zoom, Google Meet, Microsoft Teams, Webex or GoTo Meeting link. example "https://teams.microsoft.com/l/meetup-join/…"
`title`	`string`	up to 200 characters
`clientId`	`string (uuid)`nullable	The client to file it against.
`joinAt`	`string (date-time)`	When to join. Now if left out.

Responses

201 Created, `application/json`

Body: object (MeetingDetail).

A meeting with its transcript and the Tolvi AI write-up: summary, takeaways, next steps, open questions and a draft follow-up email.

201 Created response for POST /api/v1/meetings
Field	Type	Description
`id`required	`string (uuid)`
`title`required	`string`
`clientId`required	`string (uuid)`nullable
`clientName`required	`string`nullable
`platform`required	`string (MeetingPlatform)`nullable	One of: `zoom`, `google_meet`, `microsoft_teams`, `webex`, `goto_meeting`
`meetingUrl`required	`string (uri)`
`joinAt`required	`string (date-time)`
`source`required	`string (MeetingSource)`	link: pasted on the Meetings page. calendar: ticked on the Calendar page. One of: `link`, `calendar`
`status`required	`string (MeetingStatus)`	scheduling: being sent to Recall. scheduled: will join at joinAt. joining, waiting_room (someone must admit it), in_call, recording. processing: the call ended; the transcript and summary are on their way. ready: transcript and summary filed. failed: see statusDetail. cancelled. One of: `scheduling`, `scheduled`, `joining`, `waiting_room`, `in_call`, `recording`, `processing`, `ready`, `failed`, `cancelled`
`statusDetail`required	`string`nullable	Why it failed or is held up, in words.
`startedAt`required	`string (date-time)`nullable
`endedAt`required	`string (date-time)`nullable
`createdById`required	`string (uuid)`nullable
`createdByName`required	`string`nullable
`outputStatus`required	`string (MeetingOutputStatus)`	One of: `pending`, `transcribing`, `summarising`, `ready`, `failed`
`actionCount`required	`integer`	at least 0
`openActionCount`required	`integer`	Next steps not yet sorted with Create follow-ups (made into a review point or a client request, or skipped). at least 0
`recordingDeletedAt`required	`string (date-time)`nullable	When the recording (audio and video) was deleted at Recall. Tolvi keeps only the transcript and summary.
`billableMinutes`required	`integer`nullable	Minutes this meeting counts against the firm’s monthly allowance: the recording’s length, rounded up. Null until it ends. at least 0
`summary`required	`string`nullable
`keyPoints`required	`array of string`	Takeaways: facts, figures and decisions worth keeping on the client file.
`actions`required	`array of MeetingAction`	Next steps: what each side agreed to do.
`actions[].text`required	`string`
`actions[].owner`required	`string`nullable	As named in the meeting.
`actions[].side`required	`string (MeetingActionSide)`	One of: `firm`, `client`, `unclear`
`actions[].due`required	`string`nullable	As said in the meeting, e.g. "by Friday".
`openQuestions`required	`array of string`	Questions raised in the meeting that were not settled. Empty for meetings summarised before 25 Oct 2026.
`followUpEmail`required	`object (MeetingFollowUpEmail)`nullable	A draft email to the client recapping the meeting, with any client requests from Create follow-ups listed before the sign-off; null if nothing was agreed. Tolvi never sends it.
`followUpEmail.subject`required	`string`
`followUpEmail.body`required	`string`	Plain text.
`transcript`required	`array of MeetingTurn`
`transcript[].speaker`required	`string`
`transcript[].startSeconds`required	`integer`	Seconds from the start of the recording. at least 0
`transcript[].text`required	`string`
`aiTokens`required	`integer`nullable	Tolvi AI tokens the summary used. at least 0
`outputFailure`required	`string`nullable
`followUps`required	`array of MeetingFollowUp`	What each next step became (Create follow-ups), by its position in actions.
`followUps[].actionIndex`required	`integer`	The next step’s position in actions (from 0). at least 0
`followUps[].kind`required	`string (MeetingFollowUpKind)`	One of: `review_point`, `client_request`, `skip`
`followUps[].engagementId`required	`string (uuid)`nullable
`followUps[].reviewPointId`required	`string (uuid)`nullable
`followUps[].sectionCode`required	`string`nullable	The W/P section the review point is on (null: the engagement as a whole).
`followUps[].text`required	`string`nullable	Client requests: the line added to the follow-up email.
`followUps[].createdAt`required	`string (date-time)`
`followUps[].createdById`required	`string (uuid)`nullable

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 409 Conflict, 422 Unprocessable content, 429 Too many requests, as problem details (application/problem+json).

Get this month’s recorded minutes against the firm’s allowance

GET/api/v1/meetings/usage

Scopes: meetings:read

Each meeting counts its recording’s length, rounded up to the minute, in the month it started. Part of the meetings product: the firm must have it and you must have access to it.

Responses

200 OK, `application/json`

Body: object (MeetingsUsage).

Recorded minutes this month against the firm’s Meetings allowance.

200 OK response for GET /api/v1/meetings/usage
Field	Type	Description
`month`required	`string`	The calendar month (UTC). example "2026-10"
`minutesUsed`required	`integer`	at least 0
`planId`required	`string`nullable	Null on a trial (300 minutes). example "meetings_team"
`allowance`required	`integer`	at least 0
`remaining`required	`integer`	at least 0
`overageMinutes`required	`integer`	Minutes beyond the allowance; billed at 3p each on a paid plan. Recording never stops. at least 0
`thresholdsReached`required	`array of number`	80 and 100 once reached.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 429 Too many requests, as problem details (application/problem+json).

Get a meeting with its transcript, summary and actions

GET/api/v1/meetings/{id}

Scopes: meetings:read

Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for GET /api/v1/meetings/{id}
Name	In	Type	Description
`id`required	path	`string (uuid)`

Responses

200 OK, `application/json`

Body: object (MeetingDetail).

A meeting with its transcript and the Tolvi AI write-up: summary, takeaways, next steps, open questions and a draft follow-up email.

The fields are as shown above.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 404 Not found, 429 Too many requests, as problem details (application/problem+json).

Rename a meeting or file it against a client

PATCH/api/v1/meetings/{id}

Scopes: meetings:write

Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for PATCH /api/v1/meetings/{id}
Name	In	Type	Description
`id`required	path	`string (uuid)`

Request body

Required. application/json: object (UpdateMeetingRequest).

Request body for PATCH /api/v1/meetings/{id}
Field	Type	Description
`title`	`string`	up to 200 characters
`clientId`	`string (uuid)`nullable

Responses

200 OK, `application/json`

Body: object (MeetingDetail).

A meeting with its transcript and the Tolvi AI write-up: summary, takeaways, next steps, open questions and a draft follow-up email.

The fields are as shown above.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 404 Not found, 429 Too many requests, as problem details (application/problem+json).

Turn next steps into follow-ups

POST/api/v1/meetings/{id}/follow-ups

Scopes: meetings:write
Retries: Send an Idempotency-Key to make retries safe.

For a filed meeting with a ready write-up: each chosen next step becomes a review point on one of the client’s engagements (needs a reviewer, manager or partner, the review:write scope and Working Papers), a request listed in the follow-up email, or is skipped. Review points are raised exactly as in the engagement, with the meeting as their source. A step already sorted the same way is left alone; sorting it differently is refused (409). Nothing is signed off. Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for POST /api/v1/meetings/{id}/follow-ups
Name	In	Type	Description
`id`required	path	`string (uuid)`
`Idempotency-Key`	header	`string`	A unique key (1-255 visible characters) to make retries safe. Replayed for 24 hours. 1 to 255 characters

Request body

Required. application/json: object (CreateMeetingFollowUpsRequest).

Request body for POST /api/v1/meetings/{id}/follow-ups
Field	Type	Description
`engagementId`	`string (uuid)`	The engagement the review points go on: one of the filed client’s. Required when any item is a review_point.
`items`required	`array of MeetingFollowUpItem`	1 to 50 items
`items[].actionIndex`required	`integer`	The next step’s position in the meeting’s actions (from 0). at least 0
`items[].kind`required	`string (MeetingFollowUpKind)`	review_point: raised on the engagement (reviewers, managers and partners). client_request: listed in the follow-up email. skip: nothing, but the step counts as sorted. One of: `review_point`, `client_request`, `skip`
`items[].sectionCode`	`string`nullable	review_point: the W/P section; null or left out for the engagement as a whole. example "J"
`items[].text`	`string`	The wording to use instead of the next step’s own. up to 2000 characters
`items[].due`	`string`nullable	When it is due, in words; added to the point or request. up to 100 characters; example "by Friday"
`items[].mentionUserId`	`string (uuid)`nullable	review_point: a person to @mention on it.

Responses

200 OK, `application/json`

Body: object (MeetingDetail).

A meeting with its transcript and the Tolvi AI write-up: summary, takeaways, next steps, open questions and a draft follow-up email.

The fields are as shown above.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 404 Not found, 409 Conflict, 422 Unprocessable content, 429 Too many requests, as problem details (application/problem+json).

Stop the note-taker

POST/api/v1/meetings/{id}/cancel

Scopes: meetings:write

Before it joins, it is cancelled. In the call, it leaves and what it recorded so far is still transcribed. Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for POST /api/v1/meetings/{id}/cancel
Name	In	Type	Description
`id`required	path	`string (uuid)`

Responses

200 OK, `application/json`

Body: object (MeetingDetail).

A meeting with its transcript and the Tolvi AI write-up: summary, takeaways, next steps, open questions and a draft follow-up email.

The fields are as shown above.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 404 Not found, 429 Too many requests, as problem details (application/problem+json).

Get your connected calendar and its upcoming meetings

GET/api/v1/me/calendar

Scopes: meetings:read

The next 28 days. A note-taker joins only the meetings you tick. Each event says if a colleague already sent a note-taker to it, and suggests a client whose name is in its title. Part of the meetings product: the firm must have it and you must have access to it.

Responses

200 OK, `application/json`

Body: object (MyCalendar).

Your connected calendar and its upcoming meetings.

200 OK response for GET /api/v1/me/calendar
Field	Type	Description
`available`required	`boolean`
`connected`required	`boolean`
`status`required	`string`nullable	connecting, connected or disconnected.
`platform`required	`string (CalendarPlatform)`nullable	One of: `microsoft_outlook`
`email`required	`string`nullable
`events`required	`array of CalendarEvent`
`events[].id`required	`string`
`events[].title`required	`string`
`events[].startTime`required	`string (date-time)`
`events[].endTime`required	`string (date-time)`
`events[].meetingUrl`required	`string`nullable
`events[].platform`required	`string (MeetingPlatform)`nullable	One of: `zoom`, `google_meet`, `microsoft_teams`, `webex`, `goto_meeting`
`events[].notetaker`required	`boolean`	A note-taker will join: you ticked it.
`events[].meetingId`required	`string (uuid)`nullable
`events[].clientId`required	`string (uuid)`nullable
`events[].clientName`	`string`nullable	The name of the client the meeting is filed against.
`events[].takenBy`required	`string`nullable	A colleague already sent a note-taker to this meeting: their name.
`events[].suggestedClientId`	`string (uuid)`nullable	A client whose name is in the meeting’s title: a suggestion for filing it.
`events[].suggestedClientName`	`string`nullable

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 429 Too many requests, as problem details (application/problem+json).

Disconnect your calendar

DELETE/api/v1/me/calendar

Scopes: meetings:write
Access: A signed-in Tolvi session only, never an API token.

Note-takers scheduled from it are cancelled. Part of the meetings product: the firm must have it and you must have access to it.

Responses

204 No content

Disconnected.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 429 Too many requests, as problem details (application/problem+json).

Start connecting your Outlook calendar

POST/api/v1/me/calendar/connect

Scopes: meetings:write
Access: A signed-in Tolvi session only, never an API token.

Returns Microsoft’s sign-in URL. Tolvi asks only to read your calendar. Part of the meetings product: the firm must have it and you must have access to it.

Responses

200 OK, `application/json`

Body: object (CalendarConnectStart).

200 OK response for POST /api/v1/me/calendar/connect
Field	Type	Description
`authorizeUrl`required	`string (uri)`	Send the browser here to sign in to Microsoft.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 429 Too many requests, as problem details (application/problem+json).

Send a note-taker to a calendar meeting

PUT/api/v1/me/calendar/events/{eventId}/notetaker

Scopes: meetings:write

It joins when the meeting starts and follows the meeting if it moves. Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for PUT /api/v1/me/calendar/events/{eventId}/notetaker
Name	In	Type	Description
`eventId`required	path	`string (uuid)`	The calendar event id from GET /me/calendar.

Request body

Required. application/json: object (CalendarNotetakerRequest).

Request body for PUT /api/v1/me/calendar/events/{eventId}/notetaker
Field	Type	Description
`clientId`	`string (uuid)`nullable	The client to file it against.

Responses

200 OK, `application/json`

Body: object (MeetingDetail).

A meeting with its transcript and the Tolvi AI write-up: summary, takeaways, next steps, open questions and a draft follow-up email.

The fields are as shown above.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 404 Not found, 429 Too many requests, as problem details (application/problem+json).

Stop sending a note-taker to a calendar meeting

DELETE/api/v1/me/calendar/events/{eventId}/notetaker

Scopes: meetings:write

Part of the meetings product: the firm must have it and you must have access to it.

Parameters

Parameters for DELETE /api/v1/me/calendar/events/{eventId}/notetaker
Name	In	Type	Description
`eventId`required	path	`string (uuid)`	The calendar event id from GET /me/calendar.

Responses

204 No content

It won’t join.

Errors: 400 Bad request, 401 Unauthorised, 403 Forbidden, 404 Not found, 429 Too many requests, as problem details (application/problem+json).

Meetings

List meetings

Parameters

Responses

200 OK, application/json

Send a note-taker to a meeting

Parameters

Request body

Responses

201 Created, application/json

Get this month’s recorded minutes against the firm’s allowance

Responses

200 OK, application/json

Get a meeting with its transcript, summary and actions

Parameters

Responses

200 OK, application/json

Rename a meeting or file it against a client

Parameters

Request body

Responses

200 OK, application/json

Turn next steps into follow-ups

Parameters

Request body

Responses

200 OK, application/json

Stop the note-taker

Parameters

Responses

200 OK, application/json

Get your connected calendar and its upcoming meetings

Responses

200 OK, application/json

Disconnect your calendar

Responses

204 No content

Start connecting your Outlook calendar

Responses

200 OK, application/json

Send a note-taker to a calendar meeting

Parameters

Request body

Responses

200 OK, application/json

Stop sending a note-taker to a calendar meeting

Parameters

Responses

204 No content

200 OK, `application/json`

201 Created, `application/json`

200 OK, `application/json`

200 OK, `application/json`

200 OK, `application/json`

200 OK, `application/json`

200 OK, `application/json`

200 OK, `application/json`

200 OK, `application/json`

200 OK, `application/json`