Skip to main content
The Notifications API enable partners to receive asynchronous webhook notifications when ambient session processing completes or fails. You expose an HTTPS URL that accepts inbound requests. Suki calls that URL with a signed payload so your backend can pull results or update job state without relying only on polling. Critically, your notification endpoint is called by Suki. Register and configure the webhook in your partner setup, then verify signatures before you trust the payload.

​
Available endpoints

POST Ambient Session Asynchronous Notifications

Purpose: Review the webhook contract for ambient session notifications.

Webhook Overview

Learn how Partner webhooks deliver asynchronous session updates.

Signature Verification

Verify webhook signatures before you process the payload.

Webhook Configuration

Configure your notification URL and partner webhook settings.

​
Common use cases

Advance chart workflows when generation completes

Receive webhook notifications when ambient processing finishes so your backend can retrieve content and update job state without polling.

Handle failed or timed-out sessions

React to failure and timeout notifications so clinicians and operations see accurate visit status.

Secure inbound webhook traffic

Verify webhook signatures before trusting payloads that change session or job state in your system.

Fetch content from notification links

Use payload links to retrieve status or clinical content for the ambient session that just completed.
Last modified on September 29, 2026