Skip to main contentSuki’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.
Enhancements
- Added Code Examples: Added code examples in Python and TypeScript for all of the SDP APIs
- Improved the information architecture of the API reference documentation for a better developer experience
New Endpoints
-
New Info Endpoints: Introduced three new info endpoints to provide supported enum values, helping you validate context data before submission
-
Added a new API Reference Guidelines page. Refer this page to understand our API status tags, versioning, and documentation standards for the API references
Enhancements
-
API Reference Documentation Enhancement: We have significantly restructured and enhanced our API reference documentation for a better developer experience
-
The Problem-Based Charting (PBC) guide has been completely rewritten with a clearer structure and more detailed explanations of the processing pipeline
-
The Audio Streaming API Reference documentation now includes detailed authentication guidance for both browser and non-browser clients
-
Visit and Provider Context: The ambient session context APIs have been updated 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 are no longer supported for the diagnosis context
- Paused state is no longer supported for the ambient session
