GET
/
api
/
v1
/
ambient
/
session
/
{ambient_session_id}
/
content
Gets the content for the ambient session.
curl --request GET \
  --url https://sdp.suki-stage.com/api/v1/ambient/session/{ambient_session_id}/content \
  --header 'sdp_suki_token: <sdp_suki_token>'
{
  "structured_data": [
    {
      "data": {
        "dosage": "2 puffs",
        "medication": "albuterol"
      },
      "title": "MEDICATIONS"
    }
  ],
  "summary": [
    {
      "content": "Asthma exacerbation",
      "loinc_code": "18776-5",
      "source_transcripts": [
        "asthma",
        "exacerbation"
      ],
      "title": "ASSESSMENT AND PLAN"
    }
  ]
}
Understanding the SKIPPED StatusIf you see a session with a SKIPPED status, it means that the clinical note was not generated because the conversation transcript was empty.This status is an expected outcome if an ambient session is started but contains no audible speech (for example, a silent recording). It does not indicate a system error.Unlike a FAILED status, which indicates a processing error, SKIPPED is a successful outcome where no action was needed. You can typically filter out or ignore sessions with this status in your application’s user interface.

Headers

​
sdp_suki_token
string
required

sdp_suki_token

Path Parameters

​
ambient_session_id
string
required

ambient_session_id

Query Parameters

​
cumulative
boolean

cumulative

Response

200
application/json

Success Response

Response body for the /session/{ambient_session_id}/content endpoint