Form Filling SDK Authentication

The Form filling SDK uses a helper called SukiAuthManager from the @suki-sdk/core package. You give it the partnerId and partnerToken Suki assigned to your app. You create this helper once, then pass it to FormFillingClient in JavaScript or to FormFillingProvider in React. After sign-in works, Suki can show the Form filling experience (the hosted UI where clinicians speak and submit) inside your page. The helper also renews access when it expires. If the ID or token is wrong, or sign-in never finishes, Form filling will not open.

Prerequisites

Before you set up SukiAuthManager, you must have:

Partner ID (the partnerId value): Suki gives you this when you complete Partner onboarding.
Partner Token (the partnerToken value): The access value your program uses for this SDK. Your Suki contact explains how you get it and what it looks like.

Using SukiAuthManager for authentication

Create the helper when your app already knows partnerId and partnerToken by running the following code:

JavaScript

import { SukiAuthManager } from "@suki-sdk/core";

const authManager = new SukiAuthManager({
  partnerId: "YOUR_PARTNER_ID", // required
  partnerToken: "YOUR_PARTNER_TOKEN", // required
  environment: "staging", // optional: "staging" or "production"
  loginOnInitialize: true, // optional (default false)
  autoRegister: false, // optional (default true); when true, provider fields below are often required
  providerId: "YOUR_PROVIDER_ID", // optional; provider identifier in your system
  providerName: "YOUR_PROVIDER_NAME", // optional; full name, often required if autoRegister is true
  providerOrgId: "YOUR_PROVIDER_ORG_ID", // optional; org in your system, often required if autoRegister is true
  providerSpecialty: "FAMILY_MEDICINE", // optional
});

What SukiAuthManager does

Checks your settings before Form filling tries to open.
Signs in to Suki’s platform with your partner details.
Renews access when the SDK needs a fresh session.
Lets Suki’s hosted Form filling UI run with the right permissions.

A bad partnerId or partnerToken stops Form filling from loading. The hosted UI will not appear until sign-in succeeds.

Refer to Prerequisites for provider context and Configuration for session options after sign-in.

autoRegister defaults to true. When it is true, you must also pass providerName and providerOrgId. Set autoRegister to false unless your integration uses provider auto-registration.

You can create SukiAuthManager first and call login() when your app is ready, instead of loginOnInitialize: true.

Next steps

Refer to the Quickstart to create FormFillingClient with your auth manager.

Get Started

Integration Guides

Concepts & Feature Guides

API Reference

Resources

Form Filling SDK Authentication

Prerequisites

Using SukiAuthManager for authentication

What SukiAuthManager does

Next steps

​Prerequisites

​Using SukiAuthManager for authentication

​What SukiAuthManager does

​Sign in later with login()

​Next steps

Prerequisites

Using SukiAuthManager for authentication

What SukiAuthManager does

Sign in later with login()

Next steps