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

# Audio Dictation Overview

> Decide when Audio Dictation fits versus Aambient clinical notes, and compare Dictation APIs, Web SDK, and Dictation SDK integration paths

Audio Dictation converts provider speech into text while a session is active. Providers can dictate during a visit or into a field in your application while your product receives partial and final transcript text.

Audio Dictation is different from **Clinical documentation (ambient)**, which transcribes the visit and generates structured clinical notes, LOINC-based sections, and related outputs. Audio Dictation gives you **speech-to-text** you can route into your own UI, EHR fields, or downstream workflows.

## When to use Audio Dictation

Choose Audio Dictation when you need:

* Real-time transcription without generating a full ambient clinical note.
* Transcript text you control in your application (display, edit, save, or send elsewhere).
* Browser-based Dictation with Suki-managed UI (Web SDK or Dictation SDK), or full control with REST and WebSocket APIs.

<Tip>
  Choose [Ambient clinical documentation](/documentation/concepts/ambient-clinical-notes/ambient-documentation) when you need visit capture, note generation, structured clinical data, and related ambient outputs.
</Tip>

## Developer workflow

The Audio Dictation developer workflow is shared by Dictation APIs, Web SDK, and Dictation SDK. The only difference is who owns each step.

```mermaid actions={false} theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
flowchart LR
    A[Start Dictation<br/>for a UI target] --> B[Capture or stream<br/>provider speech]
    B --> C[Receive partial and<br/>final transcripts]
    C --> D[Insert text into<br/>active target]
    D --> E[Provider reviews<br/>and saves]

    style A fill:#FFF394,stroke:#333,color:#000
    style B fill:#FFF394,stroke:#333,color:#000
    style C fill:#FFF394,stroke:#333,color:#000
    style D fill:#FFF394,stroke:#333,color:#000
    style E fill:#FFF394,stroke:#333,color:#000
```

<Steps>
  <Step title="Start Dictation">
    Start a Dictation session for a field, note section, or scratchpad in your UI. With Partner APIs, create the session over REST. With Web SDK or Dictation SDK, start Dictation through the SDK controls or hosted experience.
  </Step>

  <Step title="Capture Speech">
    Capture provider speech while Dictation is active. Partner APIs stream audio over WebSocket on `GET /ws/transcribe`. Web SDK and Dictation SDK handle browser capture for you.
  </Step>

  <Step title="Receive Transcripts">
    Receive partial and final transcript text as the provider speaks. Partner APIs deliver transcript frames on the WebSocket. SDKs deliver text through events or callbacks.
  </Step>

  <Step title="Insert Text">
    Insert the transcript into the active target in your application. Your product owns field focus, rendering, and where the text lands.
  </Step>

  <Step title="Review and Save">
    Let the provider review and correct the text, then save it in your application or EHR workflow.
  </Step>
</Steps>

The steps above stay the same across products. What changes is how much you build yourself. With Dictation APIs, your application creates the session, streams audio, and handles transcript frames. With Web SDK or Dictation SDK, Suki handles more of capture and UI. In every case, your application still decides where final text lands and how you save it.

If you are building with Partner APIs, follow [Dictation basic usage](/documentation/how-to/dictation/dictation-basic-usage). To choose a modality and design the clinician experience, see the [Audio Dictation guide](/documentation/concepts/dictation/dictation).

## Related guides and resources

<CardGroup cols={3}>
  <Card title="Audio Dictation Guide" icon="microphone" href="/documentation/concepts/dictation/dictation" arrow={true}>
    Capabilities, common use cases, how Dictation works, and how to choose APIs, Web SDK, or Dictation SDK.
  </Card>

  <Card title="Audio Dictation API Basic Usage" icon="code" href="/documentation/how-to/dictation/dictation-basic-usage" arrow={true}>
    Step-by-step Partner API workflow: create a session, stream audio, receive transcripts, and end the session.
  </Card>

  <Card title="Dictation Audio Streaming" icon="wifi" href="/documentation/how-to/audio-streaming/dictation-streaming" arrow={true}>
    How to stream Dictation audio on `GET /ws/transcribe`, with links to wire format and transcript frames.
  </Card>
</CardGroup>

## Related SDKs and APIs documentation

Refer to these guides when you already know your integration path and want to dive deeper:

<CardGroup cols={3}>
  <Card title="Dictation API References" icon="code" href="/api-reference/audio-transcription/create-session" arrow={true}>
    REST and WebSocket references for transcription sessions.
  </Card>

  <Card title="Web SDK for Audio Dictation" icon="js" href="/web-sdk/dictation-overview" arrow={true}>
    JavaScript and React libraries with Suki Web SDK packages.
  </Card>

  <Card title="Dictation SDK" icon="window" href="/dictation-sdk/introduction" arrow={true}>
    Hosted iframe with Suki Dictation SDK packages.

    <Note>
      This SDK is currently in <Badge color="yellow" size="sm" icon="sparkles">Beta</Badge> and is not yet generally available.
    </Note>
  </Card>
</CardGroup>

## Next steps

<Icon icon="file-lines" iconType="solid" /> Complete the [Partner onboarding](/documentation/get-started/partner-onboarding) process and get your credentials.