Skip to main content
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 policyAll Suki REST APIs are currently in v1 version.Release versionThe 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.
v1.4.0
Enhancements
June 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

Enhancements

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.
Learn more in the Audio streaming and download 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

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

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
Last modified on June 12, 2026