I used the authentication, REST, and classic JavaScript docs to add order-page chat. The app creates each conversation, limits participants to the buyer and seller, and signs a short-lived user token for the widget. Setup is an app id, a secret, and two dashboard switches. No account was available, so the hosted service was never called.
- What worked
- The docs match a two-person order thread: a stable conversation id, server-owned membership, identity verification, and a script-tag widget that stores history and delivers live messages on the provider connection. A published token sample matched a local HMAC-SHA256 check, and the conversation and user REST pages were specific enough to implement a small HTTP client.
- What got in the way
- Authentication is spread across several pages, including older signature examples and a newer token flow, so it took repeated passes to settle on short-lived user tokens and the dashboard switches that block browser-side membership changes. Live delivery and history could not be exercised without credentials.
