Integration Paths Overview

Suki for Partners offers Ambient, Dictation, Form filling, and Patient Summary workflows. Learn more about each workflow and how to choose the right APIs or SDKs for your use case

With Suki for Partners, you can create Ambient, Dictation, Form filling, and Patient Summary workflows. Choose the APIs or SDKs that best fit your application type, stack, and how much user interface you want to own.

Use this page after you know what you are building on Introduction. Next, open the product quickstart and complete the minimum working integration before optional features.

Choose your integration path

Decide when and for which use cases you want to use the different APIs and SDKs.

Ambient & Dictation Workflows + Use Cases

Use ambient workflows to add ambient clinical intelligence to your application for doctor-patient conversations.

Ambient APIs

REST | WebSocket | Webhooks

Install Skill v1.1

CopiedCopy promptOpen in Cursor

Web SDK

JavaScript | React | Headed

Install Skill v1.1

CopiedCopy promptOpen in Cursor

Mobile SDK

iOS | Swift

Install Skill v1.1

CopiedCopy promptOpen in Cursor

Headless Web SDK

React | Headless

Install Skill v1.1

CopiedCopy promptOpen in Cursor

Dictation SDK

JavaScript | React

Install Skill v1.1

CopiedCopy promptOpen in Cursor

---

Form Filling Workflows + Use Cases

Use Form filling workflows to capture visit conversation and populate structured medical forms in nursing and other clinical workflows.

Form Filling REST APIs

REST | WebSocket | Webhooks

Install Skill v1.1

CopiedCopy promptOpen in Cursor

Form Filling SDK

JavaScript | React | Hosted

Install Skill v1.1

CopiedCopy promptOpen in Cursor

Form filling workflows are also supported in the Web SDK.

---

Patient Summary Workflows + Use Cases

Use Patient Summary workflows to generate concise pre-visit overviews from FHIR data ingested into the Clinical Knowledge Graph (CKG).

Patient Summary APIs

REST | CKG

Install Skill v2.4

CopiedCopy promptOpen in Cursor

Patient Summary workflows are also supported in the Web SDK.

What should I use to integrate Suki

The table below compares what you build yourself with direct API calls versus what the SDKs handle for you. Use it to decide how much of the integration you want to own.

Area	Direct API calls (REST, WebSocket, Webhooks)	SDKs (Web, Headless Web, Mobile, Dictation, Form filling)
Authentication	You implement token exchange, storage, headers, and refresh logic.	The SDK sets up authentication and applies your token for you.
Session lifecycle	You call the create, update, status, and end endpoints directly.	You use SDK methods or hooks for common session actions.
Audio streaming	You manage WebSocket connections, audio chunks, events, and reconnects.	The SDK manages recording, streaming, and session events.
User interface	You build every screen, control, and workflow state.	The Web SDK and Form filling SDK include a hosted UI. The Headless Web SDK, Mobile SDK, and Dictation SDK handle integration behavior while you own the layout.
Type safety	You validate request and response data in your own code.	You get typed methods, options, and events.
Error handling	You parse HTTP status codes, error bodies, and WebSocket failures.	The SDK surfaces structured failure details through errors and events.
Platform fit	Works with any client, backend, or multi-platform architecture.	Fits supported web, React, iOS, Dictation, and Form filling browser workflows.
Control	Gives you maximum control over protocol behavior.	Requires less protocol code for supported integrations.

All Suki SDKs are Client SDKs. They run in the clinician’s browser or mobile app, where they handle authentication, capture audio, manage session state, and communicate with Suki over HTTPS or WebSockets.

When choosing an SDK, the primary difference is whether Suki provides the user interface or whether you build it yourself.

SDK type	Best for	Suki products
Headed (hosted UI)	You want Suki to provide the clinical UI and user experience.	Web SDK, Dictation SDK, Form Filling SDK
Headless	You want to build your own UI while using Suki for authentication, audio streaming, and session management.	Headless Web SDK, Mobile SDK

• Regardless of which SDK you use, your backend can call Suki REST APIs and receive webhooks for tasks such as session management, transcripts, notes, and structured data.
• Client SDKs and backend APIs are designed to work together as part of the same integration.
• For Patient Summary, ingest FHIR into CKG from your backend. Generate and retrieve summaries with Patient Summary APIs, or show Patient Summary on the headed Web SDK patient profile.

Related guides

Ambient & Dictation Decision Guide

Compare the API and SDK paths for Ambient and Dictation, then pick the one that fits your stack and how much UI you want to own.

Form Filling Decision Guide

Compare the API and SDK paths for Form filling, then pick the one that fits your workflow and structured data needs.

Patient Summary Decision Guide

Decide how to integrate Patient Summary APIs for pre-visit schedule and chart workflows.

Partner Onboarding

Register your organization with Suki, configure authentication, and get your Partner ID.

Available Workflows

See the Ambient, Dictation, Form filling, and Patient Summary workflows Suki supports and what each one does.