Skip to main content
The Info APIs enable partners to retrieve the specialties, encounter types, visit types, provider roles, LOINC codes, and diagnosis types Suki accepts when you register providers or create ambient sessions. Partners typically call these endpoints from their backend to populate pickers in their product and validate payloads before session or context requests. You can fetch a combined catalog from System Information or request each category through its dedicated Info endpoint. Critically, Info endpoints return supported values only. They do not create ambient sessions or generate clinical notes. Info APIs are called from your servers and authenticated with a Suki Token (sdp_suki_token). Response bodies are stable reference data you can cache on a release schedule that fits your product.

​
Available endpoints

GET System Information

Purpose: Retrieve platform system information for your integration.

GET Encounter Information

Purpose: Retrieve encounter information to look up notes, sessions, and artifact availability for an EMR encounter.

GET Supported LOINCs

Purpose: Retrieve supported LOINC codes for note sections and related fields.

GET Diagnosis Codes

Purpose: Retrieve diagnosis code reference data for ambient requests.

GET Supported Medical Specialties

Purpose: Retrieve supported medical specialties for provider registration and sessions.

GET Encounter Types

Purpose: Retrieve supported encounter types for ambient sessions.

GET Visit Types

Purpose: Retrieve supported visit types for ambient sessions.

GET Provider Roles

Purpose: Retrieve supported provider roles for ambient context.

GET Structured Data Field Types

Purpose: Retrieve the field types supported in Embedded Form templates.

Ambient Documentation

Learn how ambient sessions use encounter and specialty context.

Note Sections

See how LOINC-coded sections map into generated notes.

Specialties

Review specialty support for clinical notes.

​
Common use cases

Populate specialty and encounter pickers

Use supported catalogs so registration and session forms only offer values Suki accepts.

Validate LOINC and diagnosis inputs

Check note sections and diagnosis payloads against supported codes before you seed ambient context.

Keep client catalogs current

Refresh Info catalogs on your release cycle so specialty, encounter, and role pickers stay aligned with Suki.

Set clinician role for the visit

Apply supported provider roles when building ambient session context for the encounter.
Last modified on October 16, 2026