E/M Coding API Changelog

API product updates and announcements for the E/M Coding APIs

Suki’s API versioning policy is based on the semantic versioning standard. For example, in version 1.2.3, 1 is the major version, 2 is the minor version, and 3 is the patch version.

When we release a new API version for new features or bug fixes, we increment one of these three version components depending on the type of change introduced.

API version numbering policy

All Suki REST APIs are currently in v1 version.

Release version

The release version in this changelog page represents the incremental progress. It is not the API version. It tracks new optional fields, performance improvements, new endpoints, and other changes.

​

v1.0.0

New Endpoints

October 2026

​

New endpoints

New E/M Coding APIs (Beta) let you generate Evaluation and Management codes from partner-supplied note content for revenue cycle management workflows. Suki recommends codes for review. Your application submits the accepted code. Generation is asynchronous. Poll session status, then retrieve codes, or use the standalone E/M webhook when configured.

• E/M Coding APIs: Added standalone generate, status, and retrieve endpoints, plus a dedicated webhook notification shape.

  • POST /api/v1/em-codes.
  • GET /api/v1/em-codes/{session_id}/status.
  • GET /api/v1/em-codes/{session_id}.
  • POST /webhooks/notification/em-codes (webhook payload).

• E/M Coding with Ambient: Ambient session create now accepts artifacts: ["EM_CODES"]. Session context accepts additional patient, provider, and visit fields used for coding. Structured data responses can include em_codes, and dedicated E/M codes endpoints are available on session, encounter, and note paths.

Learn more in the E/M Coding APIs overview and the E/M Coding concept overview.