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.1.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.0.0
New Endpoints
May 2026

​
New endpoints

We introduced the form filling APIs to enable you to create and manage form-filling sessions, retrieve structured data, submit feedback, and get info about medical form templates for nursing use cases and data collection during in-person visits or virtual patient encounters.Learn more about the form filling APIs in the Form Filling API overview.
Last modified on June 12, 2026