Skip to main content

Overview

The Suki Platform offers three integration methods. Choose based on your application type and development requirements.

Integration Options

Direct APIs

Recommended for:• Backend systems and server integrations
• Custom user interfaces
• Multi-platform applications
What you build:• Complete user interface
• Authentication flow
• Audio handling

Web SDK

Recommended for:• Web-based healthcare applications
• Browser-based EHR integrations
• Applications needing pre-built UI
What’s provided:• Pre-built UI components
• Authentication handling
• Audio processing

Mobile SDK

Recommended for:• Native iOS applications
• Mobile healthcare apps
• Apps requiring native device features
Platform support:• iOS (available now)
• Android (in development)

How To Choose

  • By Project Type
  • By Team Skills
  • By Requirements
Choose Web SDK if:
  • You want pre-built clinical UI components
  • You prefer faster integration with existing React patterns
Choose Direct APIs if:
  • You need to build a completely custom user interface
  • You have specific design requirements that pre-built components can’t meet
For iOS Applications:
  • Choose Mobile SDK - provides native iOS functionality and device integration
For Android Applications:
  • Choose Direct APIs - Mobile SDK for Android is currently in development
Choose Direct APIs
  • This is your only option for server-to-server integrations
  • Provides complete control over data processing 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

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

Web SDK:
  • ES6+ compatible browsers
  • Host URLs whitelisted with Suki for SDK embedding
Mobile SDK (iOS):
  • iOS 14.0 or later
  • Xcode development environment
  • Audio recording permissions in your app
Direct APIs:
  • WebSocket client implementation capability
  • HTTPS/TLS support for secure API communication

Integration Scenarios

  • Web Applications
  • Mobile Applications
  • Backend Systems
Scenario: Existing web-based Electronic Health Record system needing ambient clinical documentationRecommended: Web SDK• Integrates directly into your existing web application
• Provides pre-built clinical note interface
• Handles audio streaming and note generation automatically
Scenario: Healthcare patient portal where providers can document encounters during telehealth visitsRecommended: Web SDK• Ready-to-use telehealth documentation interface
• Built-in audio processing for web browsers
• Seamless integration with existing patient management systems

Next Steps

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

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 clinical workflows
  • Target platform (web, iOS, Android, backend system)
  • Development timeline and resource constraints
  • Specific technical requirements or compliance needs
Contact Options:
I