session_id, generates codes asynchronously, then you poll status and retrieve em_codes.values.
These APIs are called from your servers and authenticated with a Suki Token (sdp_suki_token). Critically, the session_id from generate is an E/M coding session ID. Do not pass an ambient session ID to the E/M status or retrieve endpoints.
Available endpoints
POST Generate E/M Codes
Purpose: Start a standalone E/M coding session and receive a
session_id.GET Get Status
Purpose: Poll whether coding is
created, running, completed, or failed.GET Get E/M Codes
Purpose: Retrieve generated E/M codes for a completed session.
Related guides
Generate E/M Codes from a Note
Learn how to call generate, poll status, and retrieve standalone E/M codes.
Get the Generated E/M Codes
Learn how to read codes from standalone sessions or ambient structured data.
E/M Coding Overview
Learn when standalone coding fits your revenue cycle workflow.
E/M Coding API Quickstart
Learn the end-to-end flow for login, generate, poll, and retrieve.
Common use cases
Code an existing note without Ambient
Submit note sections you already store so Suki can recommend Evaluation and Management codes without creating an ambient session or streaming audio.
Wait for coding before RCM handoff
Poll status at reasonable intervals so your backend loads
em_codes.values only after the session reaches completed.Feed coding review with rationale
Retrieve recommended codes, levels, and MDM, time-based, or wellness features so reviewers can confirm the visit level before payer or EHR submission.
Handle failed coding sessions
Detect
failed status so your application can retry generation, surface an error to coding staff, or fall back to manual review.