Ambient Content Retrieval
Get Ambient Session Content
Retrieve generated clinical content from completed Ambient session
GET
cURL
Updated:You can now get the structured data blocks in the response of this API, including medication orders details.
cumulative query parameter to get the cumulative summary and structured data for the specified ambient session. If the query parameter is not provided, the default value is false.
You have two options for the cumulative query parameter:
boolean
Determines whether to retrieve cumulative or snapshot data.
Understanding the SKIPPED StatusIf you see a session with a
SKIPPED status, it means that the was not generated because the conversation 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. Typically filter out or ignore sessions with this status in your application’s user interface.Code examples
- Python
- TypeScript
Authorizations
Suki access token (suki_token) from Login or Register. Expires after one hour.
Headers
Optional for standard partners.
Required for:
- Bearer authentication. Use the same
provider_idreturned by the Login or Register API. - Single Auth Token authentication. Include the same
provider_idon every request assdp_provider_id.
Example:
"provider-123"
Path Parameters
UUID for the ambient session. Use the ambient_session_id returned from Create Ambient Session, or the UUID you supplied in that request.
Query Parameters
Optional. When true, return cumulative summary and structured data up to this session. When false (default), return snapshot data for this session only.
Last modified on July 23, 2026
cURL