Skip to main content
A summary gives you the key points of a recording without reading the whole transcript. You send one request and the summary comes back in the response, written in Markdown and in the language of the transcript.

Before you start

Mint an API key (see Authentication) and export it:
You also need the id of a transcription with status completed. See Retrieve and export to find one. The Python examples use the requests package (pip install requests).

1. Create the summary

Send a POST with no body. Vook writes the summary and returns it in the same response.
A successful request returns 200 with the summary:
A POST always returns completed. You see processing only when you read a summary that another request is still writing. Each transcription has one summary. Sending the POST again returns the same summary, so you can safely repeat the call. The request takes no options: the summary’s length and style are set by Vook.

2. Read the summary

Get the summary of a transcription at any time after it is created.
The fields are the same as when you create the summary. If the transcription has no summary yet, the request returns 404 with the code summary_not_found. Send the POST to create one.

If your connection drops

The summary keeps being written after your connection closes, and it is saved to the transcription. Recover it by reading it instead of waiting on a new POST:
  1. Read the summary every few seconds while status is processing.
  2. Once status is completed, the summary is in the response.
  3. If the read returns 404 summary_not_found after a processing one, the summary could not be written. Send the POST again.
A POST sent while another request is still writing the summary returns 409 with the code summary_in_progress. Read the summary until it is completed instead.

Errors

An unknown transcription id returns 404 with the code not_found. See Errors and limits for the error body and retry rules.

Continue the summary as a chat

The summary is saved as a chat titled Summary on the transcription, holding the summary as its only message. If chat is enabled for your account, the chat shows up when you list the chats of the transcription, and you can add follow-up prompts to it like any other chat.

Retention

A summary lives as long as its transcription. When you delete the transcription, its summary is deleted with it. See Data retention.

Next steps

Chat with a transcript

Ask your own questions about a transcription.

API Reference

Try every endpoint interactively in the playground.