Skip to main content
No. ambient_session_id is the ID, not an Ambient session from the Ambient API.
Common causes:
  • Container has zero height
  • CSP blocks https://sdk.suki.ai or https://sdk.suki-stage.com in frame-src
  • Invalid template IDs or partner credentials
Refer to Error handling and Configuration.
The SDK emits SUKI_FF_001 through SUKI_FF_004, each with a reason string. There are no FF_SDK_* codes in the shipped package.Refer to Error handling for the full table and troubleshooting.
Fires when structured data arrives for a session that is no longer the foreground session (the result’s ambient_session_id does not match the open session), for example after the clinician closed processing or timeout and started a later session. Late results for the same open session still use form-filling:submitted / onSubmit. Handle with client.on("form-filling:background-submitted", ...) or React onBackgroundSubmit. For production saves, use your webhook.
Refer to Prerequisites.
Last modified on July 23, 2026