> ## Documentation Index > Fetch the complete documentation index at: https://developer.suki.ai/llms.txt > Use this file to discover all available pages before exploring further. # Welcome to Suki for Partners > Suki for Partners is Suki's developer platform for embedding Ambient Clinical Intelligence into healthcare applications with production-ready APIs and SDKs **Suki for Partners** provides production-ready APIs and SDKs to embed Ambient Clinical Intelligence (ACI) directly into healthcare applications without building speech, language, and model infrastructure yourself. Build modular, interoperable clinical AI workflows with Suki for Partners: * **Ambient documentation:** Capture patient-provider conversations and draft structured clinical notes. * **Form filling:** Extract visit conversation into structured medical form fields. * **Dictation:** Stream speech-to-text in real time for inline editing and scratchpad entry. * **Patient summaries:** Generate concise pre-visit summaries from FHIR data bundles. * **Cross-device interoperability:** Share session state across mobile and web using a shared encounter identifier. * **Modular integration:** Combine hosted UI components, headless React hooks, or REST APIs. * **Clinical intelligence:** Access ICD-10/HCC coding, LOINC note sections, Problem-Based Charting, and 80+ multilingual support. You keep your UI, branding, and workflows. Suki handles all clinical AI infrastructure and services behind your product. ## Core workflows Suki for Partners offers the following core workflows: Capture patient-provider conversations and draft structured clinical notes.
Learn More
Extract visit conversation into structured medical form fields.
Learn More
Stream speech-to-text in real time for inline editing and scratchpad entry.
Learn More
Generate concise pre-visit summaries from FHIR data bundles.
Learn More
## Get started Follow these steps to integrate Suki into your application: Select the SDK or API from the available workflows that best fits your application and integration requirements. Choose an Integration Obtain your partner credentials and configure your integration environment. Partner Onboarding Configure partner authentication so your application can securely access Suki APIs and SDKs. Set Up Authentication Follow a Quickstart to install the SDK, initialize the client, and start your first session. Quickstart ## Why choose Suki for Partners Suki for Partners provides the healthcare-specific AI, infrastructure, and APIs needed to add Ambient Clinical Intelligence to your application. Instead of building speech recognition, clinical language understanding, note generation, and supporting infrastructure yourself, you integrate Suki's production-ready platform. You keep **full control** of your application's user interface, workflows, and branding while Suki manages the clinical intelligence, AI models, security, compliance, and platform services. Whether you're building **EHRs**, **Telehealth platforms**, **Care management systems**, **Hardware solutions**, or **Revenue cycle applications**, Suki helps you add Ambient Clinical Intelligence with less development effort. Most developers choose Suki for Partners because of the following benefits: Integrate Ambient documentation, Form Filling, and Dictation using production-ready SDKs and APIs instead of building and maintaining AI infrastructure yourself. Build on a platform designed for healthcare applications with enterprise security, compliance, and operational reliability. Benefit from ongoing improvements to speech recognition, clinical language understanding, and platform capabilities without updating your own AI stack. Build your application's user interface, workflows, and integrations while Suki manages the clinical AI platform. Choose the integration approach that fits your application, including Web SDK, Headless Web SDK, Mobile SDK, Dictation SDK, Form Filling SDK, and REST APIs. Integrate with a platform that continues to evolve while maintaining backward compatibility across supported SDKs and APIs. ## Platform architecture Your app connects to Suki through client SDKs or backend REST APIs. Suki processes clinical audio with Ambient AI services, while your application integrates with FHIR / EHR systems downstream. Diagram: your application connects through SDKs and APIs to the Suki platform for Ambient AI services, and separately to your FHIR / EHR systems. Diagram: your application connects through SDKs and APIs to the Suki platform for Ambient AI services, and separately to your FHIR / EHR systems. ### Typical developer workflow Most Ambient, Form filling, and Dictation integrations follow the same session lifecycle: Diagram: choose SDK or API, authenticate, start session, capture audio, AI processing on the Suki platform, then receive notes, forms, or transcripts. Diagram: choose SDK or API, authenticate, start session, capture audio, AI processing on the Suki platform, then receive notes, forms, or transcripts. ## Recommended integrations Choose the SDK or API from the available workflows that best fits your application and integration requirements. | Requirement | Recommended integration | UI | Availability | | :------------------------------------------------ | :---------------------------------------------------------------------- | :----------------- | :----------- | | Embed a pre-built Ambient UI in a web application | [Web SDK](/web-sdk/overview) | Pre-built | GA | | Build a custom React Ambient experience | [Headless Web SDK](/headless-web-sdk/introduction) | Custom | Beta | | Build a native iOS Ambient application | [Mobile SDK](/mobile-sdk/overview) | Custom | GA | | Add speech-to-text to a web application | [Dictation SDK](/dictation-sdk/introduction) | Pre-built | Beta | | Capture structured medical forms by voice | [Form Filling SDK](/form-filling-sdk/introduction) | Pre-built | Beta | | Build a server-side Ambient integration | [Ambient REST APIs](/api-reference/overview) | Custom | GA | | Generate patient summaries from FHIR data | [Patient Summary API](/documentation/concepts/patient-summary/overview) | Custom | Beta | | Build a custom Form filling experience | [Form filling APIs](/form-filling-api-reference/overview) | Custom | GA | | Build an interoperable note workflow | Web SDK, Mobile SDK, and Ambient REST APIs | Custom + Pre-built | GA | ## What can you build Build Ambient Clinical Intelligence workflows across Ambient documentation, structured forms, real-time dictation, clinical context, and more:
Subscribe to [Release notes](/updates/release-notes) for new APIs, SDKs, and platform capabilities. ## Explore SDKs and APIs Select a workflow to see the available SDKs and APIs for that workflow. **Tabs (agents):** humans see one workflow tab. All four workflows have SDK/API cards: * **Ambient Workflows:** Ambient REST APIs, Web SDK, Mobile SDK, Headless Web SDK (and related ambient paths on this tab). * **Form filling Workflows:** Form filling APIs and Form filling SDK. * **Dictation Workflows:** Dictation APIs and Dictation SDK (plus Web SDK Dictation where linked). * **Patient Summary Workflows:** Patient Summary APIs. Choose the SDK or API that matches your UI strategy and technical approach:

Ambient REST APIs

Call Suki directly from your backend when you need a custom UI, selective feature wiring, or full control of the user experience.

Use REST for session management and content retrieval, the Partner WebSocket for audio streaming, and webhooks for asynchronous completion.

Feature availability depends on your partner configuration. To confirm access, contact our{' '} Partnership team.

Web SDK

The Suki Web SDK ships hosted UI components for web healthcare apps. Add ambient note workflows without designing the full clinical UI yourself.

Headless Web SDK

Beta

For React 18+ apps that need full control over layout and branding. Use hooks and core APIs for authentication, ambient sessions, and streaming while you build every screen to match your design system.

The Headless Web SDK is currently in Beta.

Mobile SDK

The Suki Mobile SDK is a headless SDK for native mobile apps. Design your own UI while using SDK functions for note generation and session control.

The Mobile SDK currently supports iOS.

Choose the integration method that fits your UI strategy and technical approach:

Form Filling REST APIs

Use Form filling APIs when you need a custom UI, existing-system integration, or full control over capture, session lifecycle, and how structured output is saved.

Create sessions, seed context, stream audio over the shared Partner ambient WebSocket, retrieve structured form data, and submit feedback using REST endpoints.

For streaming audio and shared WebSocket behavior, see{' '} Audio streaming.

Form Filling SDK

Beta

Embed Form filling in web applications with a hosted iframe or React components when you want voice-driven medical forms without building the full Form filling API workflow yourself.

Sign in with partner credentials, call start() with your form template IDs, and receive structured JSON through SDK callbacks and your partner webhook.

The Form filling SDK is currently in Beta.

Choose the integration method that fits your UI strategy and technical approach:

Dictation REST APIs

Use Dictation APIs when you need a custom UI, existing-system integration, or full control over capture, session lifecycle, and how transcript text is returned.

Create transcription sessions, stream audio over a WebSocket, receive live transcripts, and end sessions when capture is finished.

For streaming audio and WebSocket behavior, see{' '} Dictation streaming.

Dictation SDK

Beta

Embed clinical Dictation in web applications with a hosted iframe. Use in-field mode on a specific text control or scratchpad mode for a floating Dictation UI. Integrate with JavaScript or React; you design entry points and receive transcript text through callbacks.

The Dictation SDK is currently in Beta.

Choose the integration method that fits your UI strategy and technical approach:

Patient Summary REST APIs

Beta

Use Patient Summary APIs when you need a custom UI or full control over FHIR ingestion, summary generation, and how summaries are displayed.

Upload FHIR bundles to the Clinical Knowledge Graph (CKG), trigger asynchronous summary generation, poll job status, and retrieve full or pre-visit summaries using REST endpoints.

For CKG Data Ingestion and summary retrieval details, see{' '} CKG Data Ingestion.