livechat
livechat

Report Widget Voice Failure

Record a livechat-widget voice failure so it reaches Sentry.

WHY THIS EXISTS: the embedded widget aliases @sentry/nextjs to a no-op stub (frontend/src/livechat-widget/sentry-stub.ts — the Next SDK can't be bundled into a third-party-site IIFE without dragging Next/process in and crashing the voice path, PR #3107). So the browser's captureVoiceStartError reports NOTHING: visitors saw only a red banner and we were blind. On 2026-07-28 a lost NAT rule for the LiveKit media port broke voice for every visitor and produced ZERO Sentry issues — it surfaced only through client complaints. The widget now POSTs here and the BACKEND (whose Sentry works) reports it.

Auth: the visitor session token — the same gate as voice/dispatch — plus the origin check, so this is not an open write-to-Sentry endpoint. Reporting itself is best-effort: a telemetry failure must never propagate back into the visitor's call path, so the body is wrapped and the endpoint still 204s.

post/api/livechat/public/{widget_key}/voice/report-failure

Request

  • Base URL: https://api.dialogbrain.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.dialogbrain.com/api/livechat/public/{widget_key}/voice/report-failure
  • Auth: none declared

Path parameters

widget_keystring required

Headers

X-Session-Tokenstring nullable

Request body

error_namestring nullable
error_messagestring nullable
call_idstring nullable
stagestring nullable
http_statusinteger nullable
browserstring nullable
user_agentstring nullable
in_app_browserstring nullable
mic_permissionstring nullable
secure_contextboolean nullable
media_devices_presentboolean nullable
user_activationboolean nullable

Response

Successful Response

Changes

No recorded changes to this operation across all 5 revisions of this API.