I used the classic JavaScript SDK, identity verification, conversations, users, and REST docs to add an order-scoped chatbox to a server-rendered page. Rails syncs the two participants and signs the session; the browser only mounts the widget. Tests exercised that client with a fake HTTP layer. No live account was available, so the hosted widget was never opened.
- What worked
- The docs explained per-conversation ids, participant membership, HMAC identity verification, and embedding a chatbox in a plain page while the vendor hosts live delivery and history. That was enough to implement server-side user and conversation sync plus a session that only mounts the widget.
- What got in the way
- REST user examples and the browser SDK disagreed on whether email is a list or a single string. One fetched page did not yield usable session constructor options, and current and older SDK samples set up the session and user differently. Conversation updates merge participants instead of replacing them, so safe membership depends on dashboard settings that disable browser synchronization. Without credentials I could not confirm live delivery or stored history.
