> ## 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.

# Quickstart

> Step-by-step guide to integrate Suki's Ambient APIs and SDKs into your healthcare application

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 <Tooltip tip="A single, time-bound instance of an ambient recording for a specific patient encounter that captures clinical conversations." cta="View in Glossary" href="/Glossary/a">ambient session</Tooltip> in just a few steps.

<Note>
  **New to Suki?**

  Consider following our comprehensive [Learning path](/documentation/tutorials/learning-path) for a structured, step-by-step journey from onboarding to production deployment with progress tracking and time estimates.
</Note>

**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 <Tooltip tip="The structured medical documentation produced for a patient encounter. In Suki, ambient note generation organizes content into LOINC-coded sections so partners can review, edit, and submit notes into an EHR-ready workflow." cta="View in Glossary" href="/Glossary/c">clinical note</Tooltip> with <Tooltip tip="The text version of recorded audio from clinical conversations, generated by automatic speech recognition." cta="View in Glossary" href="/Glossary/t">transcript</Tooltip>

**Estimated Time:** 30-45 minutes for each integration path.

<Tip>
  **Using an AI coding tool?**

  Copy the following prompt to add the Suki developer documentation as a skill and [MCP server](/documentation/references/mcp) 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](/documentation/references/ai-optimized-documentation).

  <Prompt description="Install the Suki developer docs as a skill to get context on Suki's developer tools, APIs, and SDKs. Add the [MCP server](/documentation/references/mcp) for documentation search." icon="gear" iconType="regular" actions={["copy", "cursor"]}>
    Install the Suki developer docs as skill to get context on Suki's developer tools, APIs, and SDKs.

    npx skills add [https://developer.suki.ai](https://developer.suki.ai)

    Then add the Suki developer docs MCP server for access to documentation search. Follow the MCP instructions at [https://developer.suki.ai/documentation/references/mcp](https://developer.suki.ai/documentation/references/mcp).
  </Prompt>
</Tip>

## Before you begin: Prerequisites

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

<CardGroup cols={2}>
  <Card title="OAuth-Compliant Authentication System" icon="shield-check">
    For secure user management
  </Card>

  <Card title="JWT Tokens with Consistent User Identifiers" icon="key">
    For user authentication
  </Card>

  <Card title="Publicly Accessible JWKS Endpoint" icon="link">
    For token validation
  </Card>

  <Card title="ES6 Compatible Browser" icon="globe">
    Modern browser support (for Web SDK)
  </Card>
</CardGroup>

You'll also need the following from Suki to get started:

* **<Tooltip tip="A unique identifier assigned by Suki during onboarding that links an application to its configuration in the Suki Developer Platform." cta="View in Glossary" href="/Glossary/p">Partner ID</Tooltip>**:
  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 (<Tooltip tip="JSON Web Key Set. A set of keys containing the public keys used to verify any JWT issued by the authorization server." cta="View in Glossary" href="/Glossary/j">JWKS</Tooltip>) 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](/documentation/get-started/partner-onboarding) and [Partner authentication](/documentation/how-to/partner-authentication) guides for more information.

<Warning>
  **Need Access?**

  If you don't have the required information yet, contact our [Partnership team](https://www.suki.ai/suki-partners/) to begin the onboarding process.
</Warning>

## Choose your integration path

Select the integration method that best fits your application requirements. Refer to the [Integration paths overview](/documentation/get-started/integration-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.

<Note>
  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](/documentation/concepts/ambient-clinical-notes/ambient-interoperability) for more information.
</Note>

<Tabs>
  <Tab title="Ambient Workflow" icon="waveform">
    <CardGroup cols={3}>
      <Card title="Web SDK Quickstart" icon="globe" href="/web-sdk/quickstart" arrow={true}>
        **Best for:** React or JavaScript web applications

        Pre-built UI components with automatic state management. Follow the Web SDK quickstart.
      </Card>

      <Card title="Mobile SDK Quickstart" icon="mobile" href="/mobile-sdk/overview" arrow={true}>
        **Best for:** Native iOS applications

        Native framework optimized for mobile audio capture. Start with the Mobile SDK overview.
      </Card>

      <Card title="Ambient APIs Quickstart" icon="code" href="/api-reference/quickstart" arrow={true}>
        **Best for:** Custom implementations

        Maximum flexibility with direct API control. Follow the Ambient API quickstart.
      </Card>
    </CardGroup>

    **Additional options (Beta):** Headless Web SDK and Dictation SDK.

    <CardGroup cols={2}>
      <Card title="Headless Web SDK Quickstart" icon="react" href="/headless-web-sdk/quickstart" arrow={true}>
        Ambient hooks without prebuilt UI for React apps. Follow the Headless Web SDK quickstart.
      </Card>

      <Card title="Dictation SDK Quickstart" icon="microphone" href="/dictation-sdk/quickstart" arrow={true}>
        Real-time Dictation for web apps. Follow the Dictation SDK quickstart.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Form Filling Workflow" icon="file-lines">
    <CardGroup cols={2}>
      <Card title="Form Filling SDK Quickstart" icon="react" href="/form-filling-sdk/quickstart" arrow={true}>
        **Best for:** React or JavaScript web applications

        Hosted Form filling UI with SDK callbacks and partner webhooks. Follow the Form filling SDK quickstart.
      </Card>

      <Card title="Form Filling APIs Quickstart" icon="code" href="/form-filling-api-reference/quickstart" arrow={true}>
        **Best for:** Custom implementations

        REST session lifecycle plus shared Partner WebSocket audio. Follow the Form filling API quickstart.
      </Card>
    </CardGroup>
  </Tab>
</Tabs>

<Tip>
  Still stuck? Review the [FAQs](/documentation/references/faqs/general), contact the [Support team](https://forms.suki.ai/SukiSupport/form/SukiSDKSupport/formperma/T3z7hYJ7Ph-J7JrWSN08QJn32BYjarkxqm8Lm8XFPow), or reach out to the [Partnership team](https://www.suki.ai/suki-partners/).
</Tip>

## Next steps

<Icon icon="file-lines" iconType="solid" /> Refer to the [Integration paths overview](/documentation/get-started/integration-overview) to compare API and SDK integration paths.

<Icon icon="file-lines" iconType="solid" /> Refer to the [Partner authentication](/documentation/how-to/partner-authentication) guide to set up authentication with Suki.

<Icon icon="file-lines" iconType="solid" /> Refer to the [Ambient documentation](/documentation/concepts/ambient-clinical-notes/ambient-documentation) concept to learn how ambient note generation works.

<Icon icon="file-lines" iconType="solid" /> Refer to the [Form filling overview](/documentation/concepts/form-filling/form-filling) concept to learn how Form filling workflows fit your product.