text-widget-public

Report Widget Client Error

Changed on

Relay a widget-side thrown error to Sentry.

Uses the no_enabled_check auth dep so we still capture failures when a tenant has just toggled the widget off (the cause is often the reason for the error in the first place). Returns 204 on accepted reports so sendBeacon callers never see a non-success response; FastAPI's body validation may still return 422 for malformed payloads (e.g. missing message or over-length stack).

post/api/v1/public/text-widget/client-error

Request

  • Base URL: https://api.getanana.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.getanana.com/api/v1/public/text-widget/client-error
  • Auth: none declared

Query parameters

keystring nullable

Headers

X-Widget-Keystring nullable

Request body

messagestring required
stackstring nullable
session_idstring nullable
page_urlstring nullable
user_agentstring nullable
contextobject nullable

Response

Successful Response

Changes

  • d65b8fefae34Revision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status