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
POST Create Ambient Session
Purpose: Create a new ambient session for a patient encounter
POST Seed Ambient Session Context
Purpose: Seed patient, provider, and encounter context for the session
PATCH Update Ambient Session Context
Purpose: Update context during an active ambient session
POST Ambient Session Metadata
Purpose: Attach or update metadata for an ambient session
GET Audio Streaming
Purpose: Stream visit audio over WebSocket to the Suki backend
POST End Ambient Session
Purpose: End the ambient session when recording is finished
Related guides
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 when that recording is finished so Suki can process it for review, retrieval, or webhooks. Start another session on the same encounter when the visit needs more capture.