Skip to main content
POST
Generates E/M codes for a note, outside of an ambient session.
Use this API to start a standalone E/M coding session with clinical note content from your application. Send the note sections you have, and Suki returns an E/M coding session_id. E/M code generation runs asynchronously. Check the status using Get E/M coding status, then retrieve the results with Get E/M codes. If you have configured a Webhook, you can receive a notification when generation completes instead. The sections field is required and must contain at least one section with text, while patient, provider, encounter, and diagnoses details are optional. A diagnosis is a problem already on the chart, so when you send ICD-10 or IMO, Suki uses that problem together with the note when it recommends the E/M code.
The returned session_id identifies an E/M coding session, not an ambient session. Use it only with the E/M coding status and retrieval endpoints.
To generate E/M codes as part of an ambient visit, pass artifacts: ["EM_CODES"] to Create ambient session instead. See Add E/M codes to an ambient visit.

Request body fields

Code examples

The code examples below use placeholders and the production host sdp.suki.ai only as examples. For credentials, base URLs, where to run Python or TypeScript, CORS, and cURL, refer to Using code examples in your integration in the API Reference Guidelines.

Authorizations

sdp_suki_token
string
header
required

Suki access token (suki_token) from Login or Register. Expires after one hour.

Headers

sdp_provider_id
string

Optional for standard partners.

Required for:

  • Bearer authentication. Use the same provider_id returned by the Login or Register API.
  • Single Auth Token authentication. Include the same provider_id on every request as sdp_provider_id.
Example:

"provider-123"

Body

application/json

Note sections and optional patient, provider, encounter, and diagnosis context for standalone E/M code generation.

sections
object[]
required

Note sections to code from; at least one must carry content text.

diagnoses
object

(Optional) Diagnoses for the encounter.

encounter
object

(Optional)

patient
object

(Optional)

provider
object

(Optional)

Response

Success Response

session_id
string

E/M coding session ID; use for the status and retrieval APIs.

Example:

"123dfg-456dfg-789dfg-012dfg"

Last modified on November 5, 2026