Skip to main content
POST
cURL
Updated
  • Pass emr_encounter_id to enable cross-modality ambient interoperability.
  • The response now includes composition_id. Use it as note_id with the note-level Ambient APIs.
  • The multilingual parameter is deprecated. Multilingual support is enabled by default for all ambient sessions.
Use this endpoint to create an . An ambient session is one recording for a patient (visit). One encounter can include one or more ambient sessions. Suki returns an and a . Use ambient_session_id for session-scoped operations such as context, streaming, status, and session content. Store the composition_id from the response. You will pass this value as the when you call the following note-level Ambient APIs: To learn how to use ambient across modalities, refer to the Ambient interoperability guide.
For Start Ambient UI guidance, ID handling, and fields required for interoperability, refer to Create an ambient session guide.

Request body fields

You can create an ambient session with an empty request body. Suki generates ambient_session_id and returns composition_id. Add a field when you need to control how the session is identified or grouped:
  • ambient_session_id: Supply your own session UUID.
  • emr_encounter_id: Tie the note to a patient visit for cross-modality interoperability.
  • encounter_id: Group re-ambient sessions on one note. Pass it on the first session, reuse the same value on later sessions, and store it locally. Create does not return this field.
All fields are optional when creating a standalone ambient session.
Important:
  • We recommend that recordings are at least 1 minute long. Short recordings may not contain enough information for note generation.
  • If the recording is too short, note generation may be skipped.
  • For interoperable workflows, pass a valid UUID for emr_encounter_id.
  • To continue a note on another modality, pass the existing emr_encounter_id.
  • Do not create sessions for the same emr_encounter_id at the same time. Wait at least 1 second between create requests for that encounter. Faster back-to-back creates can return a conflict.

Code examples

Authorizations

sdp_suki_token
string
header
required

Suki access token (suki_token) from Login or Register. Expires after one hour.

Headers

sdp_provider_id
string

Optional for standard partners.

Required for:

  • Bearer authentication. Use the same provider_id returned by the Login or Register API.
  • Single Auth Token authentication. Include the same provider_id on every request as sdp_provider_id.
Example:

"provider-123"

Body

application/json

Session identifiers for Ambient session create. Pass emr_encounter_id to enable cross-modality interoperability and encounter_id for re-ambient workflows.

ambient_session_id
string

Optional - UUID for this Ambient session. Suki generates one when omitted and returns it in the response.

Example:

"123dfg-456dfg-789dfg-012dfg"

emr_encounter_id
string

Optional for standalone sessions - UUID for your EMR or EHR visit. One EMR encounter can contain multiple notes. Required for cross-modality Ambient workflows.

Example:

"123dfg-456dfg-789dfg-012dfg"

encounter_id
string

Required for re-ambient workflows - Groups re-ambient sessions for one note. Reuse the same value for every re-ambient session on that note. Up to 255 characters. If omitted on the first session, Suki generates one.

Example:

"123dfg-456dfg-789dfg-012dfg"

multilingual
boolean
deprecated

Deprecated. Multilingual support is enabled by default for all Ambient sessions.

Example:

false

Response

Resource created successfully.

Identifiers returned after Ambient session create.

ambient_session_id
string

UUID for the created Ambient session. Store this for later session API calls.

Example:

"123dfg-456dfg-789dfg-012dfg"

composition_id
string

ID of the note for this session. Pass this value as note_id when you call the note-level Ambient APIs.

Example:

"123dfg-456dfg-789dfg-012dfg"

Last modified on August 26, 2026