Skip to main content
The Ambient Session Management APIs enable partners to run the ambient session lifecycle for a patient encounter. You create a session, seed or update encounter context, optionally attach metadata, stream visit audio over WebSocket, then end the session when capture is finished. These APIs are called from your servers and authenticated with a Suki Token (sdp_suki_token). Critically, ending the session is what closes capture cleanly so Suki can finish processing. Streaming alone does not replace the End Ambient Session call.

Available endpoints

Create Ambient Session

Create a new ambient session for a patient encounter

Seed Ambient Session Context

Seed patient, provider, and encounter context for the session

Update Ambient Session Context

Update context during an active ambient session

Ambient Session Metadata

Attach or update metadata for an ambient session

Audio Streaming

Stream visit audio over WebSocket to the Suki backend

End Ambient Session

End the ambient session when recording is finished

Ambient Audio Streaming

Learn how to stream ambient audio for a live session

Streaming Architecture

Learn how the Ambient streaming architecture works

Ambient Documentation

Learn how ambient sessions turn conversation into clinical notes

Common use cases

Generate clinical notes inside your existing chart

Capture the visit conversation in your product so Suki can draft the clinical note while clinicians stay in your EHR workflow.

Shape note output with visit context

Provide diagnoses, note sections, specialty, and EMR encounter details so generated notes match the visit your system already knows.

Continue one note across phone and desktop

Share an EMR encounter ID so clinicians can start capture on one modality and finish review on another without losing the note.

Finalize capture for note generation

End the ambient session cleanly when the visit finishes so Suki can process the recording for review, retrieval, or webhooks.
Last modified on July 24, 2026