Ambient & Dictation APIs Changelog

API product updates and announcements for the Ambient and Dictation APIs

Suki’s API versioning policy is based on the semantic versioning standard. For example, in version 1.2.3, 1 is the major version, 2 is the minor version, and 3 is the patch version.

When we release a new API version for new features or bug fixes, we increment one of these three version components depending on the type of change introduced.

API version numbering policy

All Suki REST APIs are currently in v1 version.

Release version

The release version in this changelog page represents the incremental progress. It is not the API version. It tracks new optional fields, performance improvements, new endpoints, and other changes.

All

​

v1.7.0

New EndpointsEnhancements

October 2026

New endpoints

• Embedded Forms: You can now send the fill-in-the-blank fields from your note templates with an ambient session and read the filled values back as key/value pairs after the note is ready. Read them for the session you just recorded, or for the latest completed session on the encounter.

  • GET /api/v1/ambient/session//structured-data/section-structured-data.
  • GET /api/v1/ambient/encounter//structured-data/section-structured-data.

• Structured data field types: You can now get the field types supported in Embedded Form templates (text, radio, multi_select, and date).

  • GET /api/v1/info/structured-data-field-types.

• Content rewrite: You can now rewrite a selected span of clinical text after finishing a Dictation session (or any plain text your application owns). Send selected_text, surrounding context, selection offsets, and one instruction (CONCISE, VERBOSE, or PATIENT_FRIENDLY). The response returns the rewritten text, selection offsets for write-back, and a request_id for support.

  • POST /api/v1/content/rewrite.

Enhancements

• Session context: Each item in sections now accepts an optional precharted_content list. Send type: "string" entries with prior section text, and type: "structured" entries with Embedded Form templates.

  • POST /api/v1/ambient/session//context.
  • PATCH /api/v1/ambient/session//context.

• Session and encounter structured data: Responses now include structured_data.section_structured_values with filled Embedded Form values. Note structured data does not include them.

  • GET /api/v1/ambient/session//structured-data.
  • GET /api/v1/ambient/encounter//structured-data.

• System information and webhooks: System information now returns structured_data_field_types, and the SUCCESS webhook includes _links.section_structured_data and _links.encounter_section_structured_data.

  • GET /api/v1/info.

Learn more in the Embedded Forms documentation and the Rewrite Dictation content documentation.

​

v1.6.0

New EndpointsEnhancements

July 2026

New endpoints

• Note-level ambient endpoints: You can now retrieve accumulated content, context, and structured data for a note across ambient sessions while using the interoperability feature. Use note_id from Create ambient session.

  • GET /api/v1/ambient/note//content.
  • GET /api/v1/ambient/note//context.
  • GET /api/v1/ambient/note//structured-data.

• List encounter notes: You can now list all notes linked to an EMR encounter for cross-modality ambient workflows.

  • GET /api/v1/ambient/encounter//notes.

• Get encounter info: You can now get an overview of the shared notes for an EMR encounter. The response includes each note’s status and timestamps, the ambient sessions under that note, and which artifacts are available ("content", "transcript", or "recording").

  • GET /api/v1/ambient/encounter//info.

Enhancements

• Create ambient session: You can now pass emr_encounter_id to enable cross-modality ambient interoperability. The response now includes note_id, which you use with the note-level ambient endpoints. The multilingual parameter is deprecated. Multilingual support is enabled by default for all ambient sessions.

  • POST /api/v1/ambient/session/create.

Learn more in the How to use ambient across modalities documentation.

​

v1.5.0

Enhancements

June 30th, 2026

Enhancements

• HCC codes: You now get HCC codes in the Structured data API and Encounter structured data API output for an ambient session and encounter.

  • GET /api/v1/ambient/session//structured-data.
  • GET /api/v1/ambient/encounter//structured-data.

• Use HCC codes in the structured data output to validate the diagnosis codes in the EMR context.

JSON

{
    "structured_data": {
        "diagnoses": {
            "values": [
                {
                    "codes": [
                        {
                            "code": "A00.0",
                            "description": "Acute myocardial infarction",
                            "type": "ICD10"
                        },
                        {
                            "code": "R05.2",
                            "description": "Hypertension, unspecified",
                            "type": "ICD10"
                        },
                        {
                            "code": "65",
                            "description": "CMS-HCC model category 65", // HCC code in the format `CMS-HCC model category <code>`
                            "type": "HCC"
                        }
                    ]
                }
            ]
        }
    }
}

If an ICD-10-CM HCC diagnosis code does not map to an HCC model category, Suki looks for general HCC codes that match the diagnosis description. If no match is found, the diagnosis is returned without an HCC code.

​

v1.4.0

Enhancements

June 12th, 2026

Enhancements

• Suki now supports Single Auth Token authentication: your backend can use one shared partner_token for all clinicians instead of a per-user token. The shared token proves your organization is authorized, but it does not identify who is signed in. If you use this model, you must send sdp_provider_id on every API call so Suki can route each call to the correct clinician.

Learn more in the Provider authentication documentation.

JSON

{
    "sdp_suki_token": "your-suki-token", // sdp_suki_token required for all API calls
    // Required with Single Auth Token auth: send sdp_provider_id on Register, Login, and every API call
    "sdp_provider_id": "doc1234567890"
}

​

v1.3.0

New Endpoints

April 2026

New endpoints

• Info endpoints: Added new endpoints to get the list of supported medication coding systems, dosage units, encounter relations, frequencies, medication timings, origins, and statuses.

  • GET /api/v1/info/orders/coding-systems.
  • GET /api/v1/info/orders/dosage-units.
  • GET /api/v1/info/orders/encounter-relations.
  • GET /api/v1/info/orders/frequencies.
  • GET /api/v1/info/orders/medication-timings.
  • GET /api/v1/info/orders/origins.
  • GET /api/v1/info/orders/statuses.

Enhancements

• Medication orders: You can now send and retrieve medication orders for an ambient session and encounter using the following endpoints.

  Structured data endpoints: These endpoints return the structured data for an ambient session and encounter.

  • GET /api/v1/ambient/session//structured-data.
  • GET /api/v1/ambient/session//encounter-structured-data.

  Context API: This endpoint allows you to update the ambient session context with new EMR context and medication orders.

  • POST /api/v1/ambient/session//context.

  Content API: This endpoint returns the content for an ambient session and encounter.

  • GET /api/v1/ambient/session//content.
  • GET /api/v1/ambient/session//encounter-content.

Payload structure:

JSON

{
    "structured_data": {
        "orders": {
            "medication_orders": {
                "values": [
                    {
                        "drug_name": "Drug Name",
                        "status": "Status",
                        "medication_code": "Medication Code",
                        "medication_code_type": "Medication Code Type"
                    }
                ]
            }
        }
    }
}

When you send medication orders to the context API, the medication orders are validated against the EMR context. If the medication orders are not valid, the context API will return an error.

Learn more in the Medication orders documentation.

​

v1.2.1

New Endpoints

March 2026

New endpoints

• Audio streaming and download: We’ve added a new endpoint for audio streaming and download from ambient sessions. Stream or download the audio recording from an ambient session.

  • GET /api/v1/ambient/session//recording.

Learn more in the Ambient session recordings documentation.

​

v1.1.1

Deprecated

Feb 2026

Deprecated

• Multilingual support: The multilingual parameter is deprecated in the Create Ambient Session endpoint. When you call create ambient session API, the multilingual support is now set to true by default.

​

v1.1.0

New Endpoints

Dec 2025

New endpoints

• Audio Dictation API: Added support for real-time audio transcription. Create transcription sessions, stream transcription data, and end sessions to get final transcripts. This enables use cases like Dictation, real-time captioning, and transcript generation.

  • POST /api/v1/transcription/session/create.
  • POST /api/v1/transcription/session//end.
  • GET /ws/transcribe.

​

v1.0.1

Enhancements

Nov 2025

Enhancements

• Code examples: Added code examples in Python and TypeScript for all APIs, making it easier to integrate with the platform regardless of your preferred programming language.

​

v1.0.0

New EndpointsEnhancements

Oct 2025

New endpoints

• Info endpoints: Introduced three new info endpoints to provide supported enum values, helping you validate context data before submission and ensuring data consistency.

  • GET /api/v1/info/encounter-types.
  • GET /api/v1/info/visit-types.
  • GET /api/v1/info/provider-roles.

• API reference guidelines: Added a new API reference guidelines page to help you understand API status tags, versioning, and documentation standards.

Enhancements

• Enhanced API documentation: Significantly restructured and enhanced API reference documentation for better developer experience, clearer organization, and improved discoverability.

• Problem-based charting guide: Completely rewritten the Problem-Based Charting (PBC) guide with a clearer structure and more detailed explanations of the processing pipeline.

• Audio streaming authentication: Added detailed authentication guidance for both browser and non-browser clients in the Audio streaming API reference documentation.

• Enhanced context support: Updated the Ambient session context APIs to support a new VisitContext schema, including fields like chief_complaint and visit_type. The provider context has also been enhanced to support provider_role.

Removed support

• SNOMED codes: SNOMED codes are no longer supported for the diagnosis context.
• Paused state: Paused state is no longer supported for ambient sessions.