> ## Documentation Index
> Fetch the complete documentation index at: https://developer.suki.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# E/M Coding Notifications API

> Receive asynchronous webhook notifications when standalone E/M coding session processing completes

The E/M Coding Notifications API enables partners to receive asynchronous webhook notifications when a standalone E/M coding session completes or fails. You expose an HTTPS URL that accepts inbound requests. Suki calls that URL with a signed payload so your backend can retrieve codes or update job state without relying only on polling.

Standalone E/M success notifications use `additional_info.session_type` set to **`EM_CODES`**. Failure notifications have no `additional_info`, so match their `session_id` against the E/M coding session IDs you saved. Critically, the payload `session_id` is the E/M coding session ID from [Generate E/M codes](https://developer.suki.ai/em-coding-api-reference/em-coding-sessions/generate.md), not an ambient session ID.

E/M Coding with an ambient session still uses the existing ambient webhook. That ambient success payload always includes the `em_codes` and `encounter_em_codes` links, and they return codes when you opted into `artifacts: ["EM_CODES"]`.

Learn more in [Notification webhook for partners](https://developer.suki.ai/documentation/webhook/overview.md). For the payload fields and how to read the codes, see [E/M Coding webhook events](https://developer.suki.ai/documentation/webhook/em-coding/overview.md).

## Available endpoints

> [card] [POST E/M Coding Asynchronous Notifications](https://developer.suki.ai/em-coding-api-reference/asynchronous/webhook.md)
>
> Purpose: Review the webhook contract for standalone E/M coding session notifications.

## Related guides

> [card] [Webhook Overview](https://developer.suki.ai/documentation/webhook/overview.md)
>
> Learn how Partner webhooks deliver asynchronous session updates.

> [card] [Signature Verification](https://developer.suki.ai/documentation/webhook/signature-verification.md)
>
> Verify webhook signatures before you process the payload.

> [card] [Webhook Configuration](https://developer.suki.ai/documentation/webhook/configuration.md)
>
> Configure your notification URL and partner webhook settings.

## Common use cases

> [card] Advance RCM workflows when codes are ready
>
> Receive webhook notifications when standalone E/M coding finishes so your backend can retrieve codes without polling.

> [card] Handle failed E/M coding sessions
>
> React to failure notifications so coding staff and operations see accurate session status.

> [card] Secure inbound webhook traffic
>
> Verify webhook signatures before trusting payloads that change E/M coding job state in your system.

> [card] Fetch codes from notification links
>
> Use payload `_links` to retrieve status or `em_codes` for the standalone E/M coding session that just completed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.