Skip to main content
This quickstart guide will help you integrate Suki’s Ambient documentation capabilities into your healthcare application. You’ll go from initial setup to your first successful in just a few steps.
New to Suki?Consider following our comprehensive Learning path for a structured, step-by-step journey from onboarding to production deployment with progress tracking and time estimates.
What you’ll accomplish in each integration path By completing the quickstart for your chosen integration path, you will:
  • Set up authentication with Suki developer tools
  • Choose and integrate your preferred SDK or API
  • Create your first ambient session with patient information
  • Record and stream audio for at least 1 minute
  • Retrieve a fully structured with
Estimated Time: 30-45 minutes for each integration path.
Using an AI coding tool?Copy the following prompt to add the Suki developer documentation as a skill and MCP server to your tool for better AI-assisted coding during the integration process. For all AI options (contextual menu, llms.txt, and skill.md), refer to AI-optimized documentation.

Install the Suki developer docs as a skill to get context on Suki's developer tools, APIs, and SDKs. Add the MCP server for documentation search.

Open in Cursor

Before you begin: Prerequisites

To integrate your application with Suki developer tools, you must meet the following requirements:

OAuth-Compliant Authentication System

For secure user management

JWT Tokens with Consistent User Identifiers

For user authentication

Publicly Accessible JWKS Endpoint

For token validation

ES6 Compatible Browser

Modern browser support (for Web SDK)
You’ll also need the following from Suki to get started:
  • : Unique identifier provided by Suki that you will use to authenticate our SDKs and APIs.

How authentication works

Suki supports the following public key sharing authentication mechanisms. You will use your own identity provider to issue the token.
  • Stored Secret - You provide your public key to Suki, and we store it securely in our database as an encrypted file.
  • JWKS URL: You host your public keys at a public JSON Web Key Set () endpoint, and Suki fetches them dynamically to verify tokens.
  • Okta - You use Okta as your Identity Provider, and Suki obtains the public key from your Okta issuer URL.
  • JWT Assertion - You share your public key as a signed JWT that follows the RFC 7523 standard. Suki then verifies this JWT using our public key.
Refer to the Partner onboarding and Partner authentication guides for more information.
Need Access?If you don’t have the required information yet, contact our Partnership team to begin the onboarding process.

Choose your integration path

Select the integration method that best fits your application requirements. Refer to the Integration paths overview to help you decide.

Pick a workflow

Select a workflow below to get started. For ambient workflows, choose Web SDK, Mobile SDK, or Ambient APIs. For Form filling workflows, choose Form filling SDK or Form filling APIs.
Ambient workflows are interoperable. You can start, continue, or review the same clinical note across Ambient APIs, Web SDK, and Mobile SDK. Refer to Ambient interoperability for more information.

Web SDK Quickstart

Best for: React or JavaScript web applicationsPre-built UI components with automatic state management. Follow the Web SDK quickstart.

Mobile SDK Quickstart

Best for: Native iOS applicationsNative framework optimized for mobile audio capture. Start with the Mobile SDK overview.

Ambient APIs Quickstart

Best for: Custom implementationsMaximum flexibility with direct API control. Follow the Ambient API quickstart.
Additional options (Beta): Headless Web SDK and Dictation SDK.

Headless Web SDK Quickstart

Ambient hooks without prebuilt UI for React apps. Follow the Headless Web SDK quickstart.

Dictation SDK Quickstart

Real-time Dictation for web apps. Follow the Dictation SDK quickstart.
Still stuck? Review the FAQs, contact the Support team, or reach out to the Partnership team.

Next steps

Refer to the Integration paths overview to compare API and SDK integration paths. Refer to the Partner authentication guide to set up authentication with Suki. Refer to the Ambient documentation concept to learn how ambient note generation works. Refer to the Form filling overview concept to learn how Form filling workflows fit your product.
Last modified on July 24, 2026