{ "audio": "UklGRiQA....", "language": ["en"], "context": { "app": { "type": "email" }, "dictionary_context": [], "textbox_contents": { "before_text": "", "selected_text": "", "after_text": "" }, // ... for a full list of available fields, see the "Request Schema" page }}
Convert speech to text using client-side authentication
POST
/
client_api
Copy
Ask AI
{ "audio": "UklGRiQA....", "language": ["en"], "context": { "app": { "type": "email" }, "dictionary_context": [], "textbox_contents": { "before_text": "", "selected_text": "", "after_text": "" }, // ... for a full list of available fields, see the "Request Schema" page }}
Convert audio to text with client-side JWT authentication. This endpoint is identical to the standard /api endpoint but uses a client token (JWT) instead of an org-level API key.
Optional list of (ISO 639-1) language codes that the user is expected to speak.Setting the list size to 1 forces the transcription into the specified language. Not providing an input attempts autodetection on full list of languages (less accurate).
Optional contextual information about the circumstances surrounding the user dictation.Flow can use these information to make its output more accurate by for example, getting names right, resolving speech ambiguities, etc.All properties are optional and will use default values if not provided.
List of recent messages in the conversation, in the chronological order. Used to identify proper context and names of things being mentioned that are not conversation participants.
{ "audio": "UklGRiQA....", "language": ["en"], "context": { "app": { "type": "email" }, "dictionary_context": [], "textbox_contents": { "before_text": "", "selected_text": "", "after_text": "" }, // ... for a full list of available fields, see the "Request Schema" page }}