Skip to main content
The Form filling Notifications API enables partners to receive asynchronous webhook notifications when Form filling 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 retrieve structured form output or update job state without relying only on polling. Form filling notifications use the same callback URL, signature verification, and configuration as ambient notifications, and the same SUCCESS and FAILURE pattern. The links are different: a Form filling success payload fills only structured_data and status, and additional_info.session_type is FORM_FILLING. Critically, Form filling notifications reference your Form filling ambient_session_id, not an ambient clinical note session ID. Learn more in Notification webhook for partners. For the payload fields and how to read the filled forms, see Form filling webhook events.

Available endpoints

POST Form Filling Asynchronous Notifications

Purpose: Review the webhook contract for Form filling 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 workflows when form output is ready

Receive webhook notifications when Form filling processing finishes so your backend can retrieve structured data without polling.

Handle failed or aborted Form filling sessions

React to failure notifications so clinicians and operations see accurate Form filling status.

Secure inbound webhook traffic

Verify webhook signatures before trusting payloads that change Form filling job state in your system.

Fetch form content from notification links

Use payload links to retrieve status or structured data for the Form filling session that just completed.
Last modified on November 5, 2026