Skip to main content
This example shows how to build a server-side webhook handler for Form filling results. onSubmit runs in the browser when structured data is ready, but it may not run if the clinician closes the tab before processing finishes. The example receives a Partner notification webhook after Suki completes backend processing, verifies the request, and fetches structured data to save to your EHR. Webhook session_id maps to ambient_session_id in the SDK. Webhook encounter_id maps to correlation_id when you pass your encounter UUID at session start.
JavaScript
Verify every request with Signature verification. Use session_id as an idempotency key. Refer to Get Form filling structured data for production URLs and auth headers.

Available cookbooks

Available tutorials

Next steps

EHR handoff - Map structured_data to your EHR fields. Session workflow - Browser vs server delivery. Webhook quickstart - Endpoint setup and testing.
Last modified on October 16, 2026