Skip to main content
This release adds Audio streaming & download so you can stream or download original ambient session audio for playback, verification, and compliance. For the Web SDK (v2.1.2), we’ve added notification webhooks for session completion and failure (no polling), existing patient diagnoses in ambientOptions so PBC notes merge EMR problems with what’s discussed in the visit, and optional session-level metadata (visit type, encounter type, provider role, reason for visit, chief complaint) to improve note generation.

What’s new

March 2026 - New
New Features
Audio streaming and download

New features

API v1.2.1Audio streaming and download: We’ve added a new endpoint to stream or download the original audio recording from an ambient session. Get a presigned URL for any completed session and use it for playback, note verification, or compliance storage.Why it matters: Enables playback in your app, verification of AI notes against the conversation, and compliance use cases that require retaining the original audio.Learn more in the Audio streaming and download guide. For the full API reference, refer to Get session recording.

What’s enhanced

March 2026 - Enhanced
Enhancements
Webhook support

Enhancements

Web SDK 2.1.2Webhook support: We’ve added notification webhook support for the Web SDK. When a session completes or fails, Suki sends a POST to your callback URL, same as when using the direct API. Configure one webhook URL per partner during onboarding.Why it matters: Receive session completion and failure notifications when using the Web SDK without polling.Learn more in the Notification webhook guide.Web SDK 2.1.2Existing patient diagnoses for Problem-Based Charting: Pass the patient’s existing diagnoses (e.g. from the EMR) into an ambient session using the diagnoses block in ambientOptions. The session merges them with what’s discussed during the visit so you avoid duplicate problems in the note. Use this when you have at least one PBC section (isPBNSection: true); each diagnosis needs one ICD-10 code.Why it matters: Seed the problem list from the EMR and get one merged note without duplicates when the provider or patient discusses those problems.Learn more in the Existing patient diagnoses guide.Web SDK 2.1.2Optional session-level metadata: Pass visit context (visitType, encounterType, reasonForVisit, chiefComplaint) and providerRole in ambientOptions to improve note generation. Pass these at session init (e.g. in mount or when calling setAmbientOptions).Why it matters: Improve note generation accuracy by passing session-level metadata.Learn more in the Optional session-level metadata guide.
Last modified on March 23, 2026