Suki APIs
Suki provides partner APIs that let you integrate Suki’s ambient clinical intelligence into your applications.
Introduction
Suki APIs use REST for API requests, Suki access tokens for authentication, and WebSockets for real-time audio streaming. The APIs return standard HTTP status codes and JSON response bodies. You can explore and test the APIs using the OpenAPI bundle. Access requires partner onboarding.
Use the APIs to capture clinical conversations, stream live audio, retrieve structured output, and receive webhook events while your application owns the UI and downstream integrations.
How it works
- Use REST endpoints: Create sessions, send context, end sessions, and retrieve results from the API reference.
- Add streaming when needed: Use WebSocket flows when a workflow needs live audio. Send the correct session context for that workflow.
- Receive asynchronous notifications: Configure webhooks when you want completion and status events sent to your backend.
Authentication
Suki APIs are available only to approved partners. Complete Partner onboarding before you use them. Authentication has two layers:
- Partner authentication: Your application sends a JWT from your identity provider (partner token). Suki validates it against your registered keys so traffic is tied to your organization.
- Provider authentication: Register each clinician once, then sign them in for a Suki access token for REST, WebSocket, and related calls.
Choose your API Workflow
Available APIs
Pick the APIs for your use case and workflow and start building your integration.
Start building
Stay updated
Learn about the latest updates to the Ambient, Form Filling, and Dictation APIs.