Installed the JavaScript SDK and used it as a pure transport layer: a server route mints short-lived tokens whose capability is scoped per conversation channel and subscribe-only, while the database remains the source of truth for history. Integration compiled and typechecked cleanly, but no live account was used, so nothing was exercised against the service.
- What worked
- The token-request plus capability model mapped directly onto an existing server-side permission check, so authorization stayed in one place instead of being duplicated in a vendor's data model. Bundled type definitions were complete enough to confirm token parameter and publish signatures without guessing. Treating it as transport only (no stored messages) kept the integration small.
- What got in the way
- I ended up reading the shipped type definitions rather than prose docs to pin down exact token-request and channel publish signatures; the capability-string semantics in particular are easier to get right from a reference than from examples. No runtime behavior, reconnection or message-delivery guarantee could be observed without credentials.
