Skip to main content

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.

Suki for Partners provides different integration paths for adding form filling capabilities to your application. Currently we offer the Form Filling APIs integration path which is designed for custom implementation approaches, and levels of UI ownership. This guide explains the available integration options for form filling workflows and helps you select the approach that best fits your application architecture, technology stack, and user experience goals. Use this guide to understand the tradeoffs between each integration path, including how much workflow logic, audio handling, and UI customization your team manages. For ambient clinical documentation and dictation workflows, please refer to the Ambient workflows integration decision guide.

​
Integration options

​
Form Filling APIs

Form Filling APIs are the most flexible integration option and allow you to build your own user interface and authentication flow for your application.

Recommended for:

• Backend systems and server integrations
• Custom user interfaces on any stack
• Multi-platform applications

What you build:

• Complete user interface
• Authentication flow
• Audio handling and API/WebSocket usage

​
How to choose

Choose Form Filling APIs if:
  • You need structured medical form output from visit conversation
  • You will build your own UI for template selection, recording, and form review
  • You want full control at the REST and WebSocket level in the browser
For iOS Applications:
  • Choose Form Filling APIs - implement REST and WebSocket in your native app or through your backend
For Android Applications:
  • Choose Form Filling APIs - same API surface with your Android client and audio capture
Choose Form Filling APIs
  • This is your primary option for server-to-server integrations
  • Provides complete control over session lifecycle, structured data, and system integration
HIPAA Compliance: All integration methods can be implemented in a HIPAA-compliant manner. Compliance depends on your implementation practices and security measures.

​
Prerequisites for all integration methods

Before integrating with any Suki Platform method, you must complete the partner onboarding process:

​
Required for all integration methods

Partner Registration:
  • Complete the Partner onboarding process
  • Receive your unique partner_id from Suki
  • Provide your JWKS endpoint URL to Suki for token validation
Authentication System:
  • OAuth 2.0 compliant authentication system
  • JWT token generation with consistent user identifier
  • Publicly accessible JWKS endpoint for token verification

​
Additional requirements by method

Form Filling APIs:
  • WebSocket client implementation capability
  • HTTPS/TLS support for secure API communication
  • Use the form-filling ambient_session_id from Create form filling session on Form Filling REST calls and on GET /ws/stream (refer to Ambient audio streaming for WebSocket wire format)

​
Integration scenarios

Scenario: Existing web-based Electronic Health Record system needing structured medical form capture during visitsRecommended: Form Filling APIs• Integrates into your existing web application
• Supports template selection and structured form output for nursing and clinical workflows
• You manage session lifecycle, audio streaming, and save logic in your EHR
Scenario: Healthcare patient portal where providers complete intake or assessment forms during telehealth visitsRecommended: Form Filling APIs• Capture visit conversation in the browser
• Retrieve structured form data when processing completes
• Seamless integration with existing patient management systems
Scenario: Web clinician workflow where form filling must match your design system, layout, and interaction patternsRecommended: Form Filling APIs• Full control over recording controls, status, and form presentation
• Seed and update session context with form_template_id values
• Stream audio on the Partner WebSocket with your form-filling session ID

​
Next steps

To begin your integration, review the documentation for your chosen approach:

Form Filling Basic Usage

Step-by-step Partner API workflow for form filling

Form Filling API Overview

Build custom form filling integrations with maximum flexibility

Form Filling API Quickstart

Get started with authentication and core API calls

Form Filling

Capabilities, use cases, and how form filling works

Partner Onboarding

Start your integration journey with Suki

​
Get personalized integration guidance

If your use case doesn’t clearly match the scenarios above, or you need specific technical advice for your healthcare application, our customer success team provides personalized consultation. Before contacting support or sales, please prepare:
  • Description of your healthcare application and form filling workflows
  • Target platform (web, iOS, Android, backend system)
  • Development timeline and resource constraints
  • Specific technical requirements or compliance needs
Contact options:
Last modified on May 22, 2026