Skip to main content
To handle different doctor roles/specialties dynamically, clients use our context API to seed with the role (e.g. SPECIALTY).
Yes. For an ambient session, a successful webhook with a session status of completed means note generation completed. A successful webhook can also arrive with a session status of skipped, when the recording was silent or too short. Suki still runs the Ambient documentation pipeline in the background, including clinical note and encounter content, even if your application only follows the transcript link afterward.The success webhook payload identifies the session and encounter and includes _links for content, transcripts, status, structured data, section structured data, E/M codes, diagnoses, and orders, at the session level and the encounter level. Using only Get Session Transcript does not skip note generation. Session status completed means the session finished and final content was generated. See Ambient webhook events and Ambient webhook payload.There is no ambient option today that returns only the conversation transcript without generating the clinical note and related encounter documentation.
Last modified on November 5, 2026