Use Info APIs

Quick summary

Suki Info APIs provide catalogs of values supported for ambient session context and Medication order context.

Use these APIs to discover supported values, populate UI controls, or validate values before you send context through seed or update. Info catalogs list what Suki accepts. They do not apply values to a session for you.

Last updated:August 2026

Suki Info APIs provide catalogs of values supported by Suki for ambient session context and Medication order context. Use these APIs when your application needs to discover supported values, populate UI controls, or validate values before sending context to Suki.

Info APIs tell you what values are supported. They do not apply those values to an ambient session.After your application selects the values it needs, send them through Provide visit context or Add information during a visit to apply them to the ambient session.

What you can use Info APIs for

Use Info APIs to:

Build pickers and dropdowns from Suki-supported values.
Validate context values before sending them to Suki.
Keep medication order fields aligned with supported metadata.
Load supported LOINC section codes for note-section mappings.
Avoid maintaining hard-coded lists of supported values in your application.

Info APIs support context preparation. They are not a replacement for the ambient session workflow. You still use the appropriate APIs to create the session, stream audio, end the session, and retrieve ambient content.

How Info APIs fit into your workflow

The typical flow is: For example, your application can:

Load supported LOINC section codes.
Use those values to populate a note-section picker.
Let the clinician select the sections that apply to the visit.
Send the selected values as ambient session context.

The Info API only provides the supported values. Your application is responsible for sending the selected values as context through Provide visit context or Add information during a visit.

Choose how to load the catalogs

You can load all available Info catalogs together or retrieve a single catalog for your application’s UI pickers.

Load Multiple Catalogs

Use System information when your application needs several catalogs.

GET /api/v1/info

This returns the Info catalogs together in a single response.

Load One Catalog

Use a dedicated Info API when your application only needs a specific category.

GET /api/v1/info/loincs

This returns the supported LOINC section codes.

Dedicated routes are available for specialties, encounter types, visit types, provider roles, diagnosis code types, and medication order metadata.

Available Info APIs

API	What it returns	Typical use
System information	All Info catalogs in one response	Load multiple catalogs together
Supported LOINCs	Supported LOINC section codes and display names	Note-section pickers and validation
Supported medical specialties	Supported medical specialties	Specialty fields
Encounter types	Supported encounter types	Encounter type fields
Visit types	Supported visit types	Visit type fields
Provider roles	Supported provider roles	Provider role fields
Supported diagnosis codes	Supported diagnosis code types	Diagnosis code fields
Medication order metadata	Medication order metadata enums	Load medication order metadata together
Medication coding systems	Supported medication coding systems	Medication coding system fields
Medication dosage units	Supported dosage units	Dosage unit fields
Medication frequency types	Supported medication frequency types	Frequency fields
Medication timings	Supported medication timings	Timing fields
Medication order statuses	Supported medication order statuses	Order status fields
Order origins	Supported order origins	Order origin fields
Order encounter relations	Supported encounter relation values	Order encounter relation fields

Use Info catalogs in your application

There are three common ways to use these catalogs.

Build UI Pickers

Load the relevant catalog and use its values to populate your application’s UI.For example, use Supported LOINCs to build a note-section picker instead of maintaining a separate list of LOINC values in your application.Similarly, use the specialty, visit type, encounter type, and provider role catalogs when your application exposes those fields.

Validate Context

If your application receives context from another system or accepts values through user input, validate those values against the relevant Info catalog before calling Provide visit context or Add information during a visit.This lets your application identify unsupported values before sending the context.

Prepare Medication Order Context

Medication order context uses supported metadata for fields such as:

Coding systems
Dosage units
Frequency types
Medication timings
Order statuses
Order origins
Encounter relations

Use Medication order metadata when you need these catalogs together, or use an individual medication order Info API when you only need one category.See Medication orders for how medication orders fit into the ambient workflow.

Info catalogs vs session context

It is important to keep these two concepts separate.

Info catalogs	Session context
Describe values supported by Suki	Contains values that apply to a specific session
Used to populate UI or validate values	Sent to Suki for the session
Retrieved through Info APIs	Sent through seed or update context APIs
Do not modify an ambient session	Provides context for the ambient session

For example, loading the supported specialties does not set a specialty on an ambient session. Your application must select the appropriate specialty and send it as session context.

Recommended implementation

Load the Catalogs You Need

Use System information when you need several catalogs. Use a dedicated Info API when you only need one.

Use the Returned Values

Use the catalog values to populate your UI or validate values before sending them.

Send the Selected Values as Context

Pass the values that apply to the visit through Provide visit context or Add information during a visit.Info APIs do not send context for you.

Cache Catalogs When Appropriate

If your application uses the same catalogs repeatedly, you can cache the responses and reuse them for pickers and validation.Choose a refresh strategy that fits your application. Refresh your cached values when you need to pick up changes to supported values, or when your application needs to use newly supported values.

You do not need to fetch an Info catalog before every ambient session if your application already has a cached copy of the catalog it needs.

Use the right catalog

Note Sections

Use Supported LOINCs to retrieve supported LOINC section codes and display names for note-section pickers and validation.If the LOINC values returned by the Info API differ from the static table in Note sections, use the Info API values. The API represents the supported values.

Specialties and Provider Roles

Use Supported medical specialties and Provider roles when your application needs supported specialty or provider role values for context.Concept guide: Specialties.

Visit and Encounter Types

Use Visit types and Encounter types when your application collects those fields for context.

Diagnosis Code Types

Use Supported diagnosis codes when your application needs the supported diagnosis code types for diagnosis context.

Medication Order Metadata

Use Medication order metadata when your application needs multiple medication order catalogs.Use the dedicated medication order routes when you only need a specific category, such as coding systems, dosage units, frequencies, timings, statuses, origins, or encounter relations.

Common mistakes to avoid

These patterns cause integration issues when teams treat Info catalogs like session context or block the ambient workflow on catalog fetches.

Using Info APIs Instead of Context APIs

Do not use an Info API instead of Provide visit context or Add information during a visit.Info APIs return supported values. The context APIs send the values that apply to the visit.

Sending Every Supported Value as Context

A catalog can contain many supported values, but only the values that apply to the current visit should be sent as session context.Load the full catalog for pickers or validation. Send only the clinician’s selections on seed or update.

Treating the Note Sections Table as Source of Truth

When the static Note sections documentation and Supported LOINCs differ, use the values returned by the Info API.The concept guide is illustrative. The LOINC Info API represents the supported values Suki accepts today.

Requiring a Catalog Fetch Before Every Session

Info APIs support context preparation. They are not a replacement for the APIs used to create, stream, end, or retrieve content from an ambient session.Your application can use cached catalog values when appropriate. Do not block Create, Stream, End, or content retrieval on a fresh Info API call when you already have the catalogs you need.

Example code to build a note-section picker

The following example retrieves supported LOINCs and reads the code and common_name values from the response.

TypeScript
Python

const response = await fetch("https://sdp.suki.ai/api/v1/info/loincs", {
  headers: {
    sdp_suki_token: sdpSukiToken,
    sdp_provider_id: sdpProviderId,
  },
});

if (!response.ok) {
  throw new Error(`Get LOINCs failed: ${response.status}`);
}

const data = await response.json();

for (const loinc of data.loincs ?? []) {
  console.log(loinc.code, loinc.common_name);
}

import requests

response = requests.get(
    "https://sdp.suki.ai/api/v1/info/loincs",
    headers={
        "sdp_suki_token": sdp_suki_token,
        "sdp_provider_id": sdp_provider_id,
    },
)

response.raise_for_status()

data = response.json()

for loinc in data.get("loincs", []):
    print(loinc.get("code"), loinc.get("common_name"))

Use the returned values to build your application’s note-section UI or validation logic. When the clinician selects a section, send the selected value through your ambient session context workflow.

What’s next

System information Load the available Info catalogs in one response. Provide visit context Send initial context to an ambient session. Add information during a visit Update context after it has been added. Note sections Learn how note sections and LOINC codes are used. Medication orders Learn how medication order context works in the ambient workflow.

Get Started

Concepts & Feature Guides

Resources

FAQs & Support

Use Info APIs

What you can use Info APIs for

How Info APIs fit into your workflow

Choose how to load the catalogs

Load Multiple Catalogs

Load One Catalog

Available Info APIs

Use Info catalogs in your application

Info catalogs vs session context

Recommended implementation

Load the Catalogs You Need

Use the Returned Values

Send the Selected Values as Context

Cache Catalogs When Appropriate

Use the right catalog

Common mistakes to avoid

Example code to build a note-section picker

What’s next

​What you can use Info APIs for

​How Info APIs fit into your workflow

​Choose how to load the catalogs

Load Multiple Catalogs

Load One Catalog

​Available Info APIs

​Use Info catalogs in your application

​Info catalogs vs session context

​Recommended implementation

Load the Catalogs You Need

Use the Returned Values

Send the Selected Values as Context

Cache Catalogs When Appropriate

​Use the right catalog

​Common mistakes to avoid

​Example code to build a note-section picker

​What’s next

What you can use Info APIs for

How Info APIs fit into your workflow

Choose how to load the catalogs

Available Info APIs

Use Info catalogs in your application

Info catalogs vs session context

Recommended implementation

Use the right catalog

Common mistakes to avoid

Example code to build a note-section picker

What’s next